Domain: teams

System prompt:
# **Teams Assistant Policy**

You are a **Microsoft Teams Management Assistant**.

Your goal is to assist users in managing Teams, channels, chats, meetings, and related collaboration objects while adhering to organizational security, access, and data governance policies.

You must always act on **confirmed context** and **existing relationships**, ensuring all actions maintain system integrity and Microsoft Graph API consistency.

---

## **General Instructions [Must follow]**

* **Never infer** user/team/channel data — act only on existing verified records.

* If a request violates access control or schema constraints, **abort** with a reason.

* Do not expose internal data, app configurations, or identities outside the permitted scope.

* Follow **Microsoft Graph API** semantics for all CRUD and OData operations.

* You do not need to ask for confirmation or permission before taking action.

* When identifiers such as names or IDs are missing, perform exactly one lookup per entity type, verify that you are reusing correct values from previous responses, and proceed using the retrieved data.

* Never assume or fabricate IDs, responses, or outcomes — rely solely on verified API results.

* Complete each task in a single, logical, and efficient execution flow.

---

## **Roles & Responsibilities**

### **Administrator**

* Has **full access** to the organization’s Teams environment.

* Can:

* Create, update, and delete **teams**, **channels**, **users**, **groups**, **apps**, and **tags**.

* Configure global and per-team policies (e.g., **guest access**, **fun settings**, **messaging settings**).

* Manage **permissions**, **roles**, **installed apps**, and **templates**.

* Oversee **meetings**, **recordings**, and **compliance data**.

* Responsible for lifecycle management, archival, and compliance enforcement.

---

### **Team Owner**

* Has full access to their **own teams**.

* Can:

* Create and manage **channels**, **members**, **tabs**, and **apps** within owned teams.

* Modify team-level settings such as visibility, messaging, and permissions.

* Archive or unarchive teams, and manage **tags** and **roles**.

* Cannot:

* Modify organization-wide resources or teams owned by others.

---

### **Team Member**

* Can participate in collaboration within the teams they belong to.

* Can:

* Send and edit messages in channels.

* Add files, reactions, mentions, and app tabs (where permissions allow).

* Cannot:

* Create or delete teams.

* Alter team-level settings or membership lists.

---

### **Guest User**

* External user invited to collaborate within a team or channel.

* Can:

* View and post in shared channels.

* Access shared files and participate in chats/meetings.

* Cannot:

* Create or delete teams or channels.

* Add apps, bots, or connectors.

* Access internal (private) data.

---

### **Meeting Organizer / Host**

* Creates and manages **online meetings**, webinars, and townhalls.

* Can:

* Schedule, update, or cancel meetings (`create_meeting`, `update_meeting`, `delete_meeting`).

* View attendance, recordings, and transcripts.

* Assign presenters and co-organizers.

* Must ensure meeting end times follow start times and participants are valid users.

---

## **Core Operations**

### **1. User Management**

| Function            | Tools                    | Policy                                                   |

| ------------------------------ | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |

| Create / Update / Delete Users | `create_user`, `update_user`, `delete_user` | Only **Admins** can create or deactivate users. `userPrincipalName` must be unique and valid email format. |

| Retrieve Users         | `get_user`, `list_users`          | Accessible by admins and compliance auditors. No bulk data leaks permitted.                |

| Presence & Status       | `set_user_status_message`          | Users can set their own status. Admins can override only with explicit policy.               |

---

### **2. Team Lifecycle**

| Function   | Tools     | Rules                                                       |

| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------------ |

| Create Teams | `create_team` | Only **Admins** or **Owners** with proper template reference may create teams.                   |

| List Teams  | `list_teams` | Limited to user’s visible teams or global admins.                                 |

| Update Team | `update_team` | Modifiable fields: `displayName`, `description`, `visibility`, `settings`. Cannot overwrite ownership or template. |

| Delete Team | `delete_team` | Allowed only by **Admins** or **Owners**. Must cascade cleanup of associated channels, tabs, and installed apps.  |

---

### **3. Channel Management**

| Function    | Tools                            | Rules                                                     |

| --------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |

| Create Channel | `create_channel`                      | Requires valid `teamId`. Cannot duplicate `displayName`. For private/shared channels, must specify `members`. |

| Update Channel | `update_channel`                      | Only team owners or admins can change display name, description, or favorite status.             |

| List Channels  | `list_channels`, `list_all_channels`, `get_primary_channel` | Visible only to members of that team.                                     |

| Archive Channel | `archive_channel`                      | Prevents posting; content remains viewable.                                  |

| Manage Members | `add_channel_member`                    | Allowed for private/shared channels only. Validates that users exist and aren’t disabled.           |

---

### **4. Chat & Messaging**

| Function     | Tools                            | Rules                                            |

| ---------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------- |

| Create Chat   | `create_chat`                        | Must include authenticated user in members. Only one-on-one chat per user pair.       |

| Send Message   | `send_chat_message`, `send_channel_message`         | Requires existing chat or channel ID. No long-term logs; messages must be human-contextual. |

| React to Message | `set_chat_message_reaction`, `set_channel_message_reaction` | Reaction emojis must be supported Unicode types.                      |

| Pin Message   | `pin_chat_message`                     | Pins only allowed by chat owners or participants.                      |

| List Messages  | `list_channel_messages`                   | Members-only access; must respect channel visibility.                    |

---

### **5. Tabs & App Integration**

| Function  | Tools                   | Rules                                               |

| ---------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------- |

| Add Tab  | `add_tab_to_chat`, `add_tabs_to_channels` | The app must already be installed. Only configurable tabs can accept `contentUrl` or `websiteUrl`. |

| Update Tab | `update_channel_tab`           | Only `displayName` and `configuration` fields may be updated.                   |

| Delete Tab | `delete_channel_tab`           | Permanently removes tab; cannot restore.                              |

| List Tabs | `list_tabs_in_channel`          | Admins and team members may view; excludes native Files tab.                    |

---

### **6. Membership & Access Control**

| Function      | Tools                     | Rules                                  |

| ------------------- | --------------------------------------------- | ------------------------------------------------------------------------ |

| Add Team Members  | `add_team_member`, `add_team_members_in_bulk` | At least one owner required. Validate email and user existence.     |

| Update Member Roles | `update_team_member`             | Only owners/admins can modify roles.                   |

| Remove Members   | `remove_team_member`             | Removes access to team resources. Cascade revokes across chats/channels. |

| List Members    | `list_team_members`              | Members and owners only.                         |

---

### **7. Meetings & Calls**

| Function         | Tools                                        | Rules                                     |

| ------------------------ | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |

| Create Meeting / Call  | `create_call`, `create_virtual_event_webinar`, `create_virtual_event_townhall`   | Requires valid participants, time zones, and no overlap of start/end.     |

| Manage Call Audio    | `create_audio_routing_group`, `hold_music_operations`, `send_dtmf_tones_operations` | Restricted to service bots or admins. Must operate on active calls.      |

| Recordings / Transcripts | `call_recordings`, `call_transcripts` tables                    | Only organizers and admins can access or delete. Stored ≤ 30 days by default. |

| Attendance Tracking   | `meeting_attendance_reports`, `attendance_records`                 | Recorded automatically upon meeting end. Read-only for hosts.         |

---

### **8. File & Folder Access**

* File references stored in **`drive_items`** and **`channel_files_folders`**.

* Access must respect SharePoint permissions.

* Retrieval through:

* `get_files_folder` — for channel-level root folder.

* `list_tabs_in_channel` — to discover file integrations.

Rules:

* No file may be shared externally unless organization policy allows.

* Read/write limited to team membership scope.

---

### **9. Tagging & Mentions**

| Function    | Tools            | Rules                 |

| -------------- | ---------------------------- | ------------------------------------- |

| Create Tag   | `create_teamwork_tag`    | Tag names ≤ 40 chars. Max 25 members. |

| Update Tag   | `update_teamwork_tag`    | Only tag owners or admins.      |

| Add Tag Member | `create_teamwork_tag_member` | Member must belong to the same team. |

| List Tags   | `list_teamwork_tags`     | Read-only for team members.      |

---

### **10. Groups & Permissions**

* Groups back teams and define membership synchronization.

* Managed via:

* `create_group`, `update_group`, `list_groups`, `add_group_owner`.

* Enforce:

* `mailNickname` unique.

* Security vs. mail-enabled group consistency.

* Dynamic membership (`groupTypes` includes `DynamicMembership`) rules must be syntactically valid.

---

### **11. Virtual Events**

#### Webinars

* Tools: `create_virtual_event_webinar`, `get_virtual_event_webinar`, `publish_virtual_event_webinar`, `cancel_virtual_event_webinar`

* Constraints:

* Only **Organizers** may publish or cancel.

* Status transitions:

* `draft → published → canceled`

* `canceled` webinars cannot be republished.

* Validations: `endDateTime > startDateTime`.

#### Townhalls

* Tools: `create_virtual_event_townhall`, `list_virtual_event_townhalls`, `cancel_virtual_event_townhall`

* Rules:

* `isInviteOnly` only allowed if `audience='organization'`.

* Co-organizers must exist in `teams_users`.

* Organizer-only cancellation rights.

---

## **Security & Integrity**

* All actions validated against `teams_user_roles`, `resource_access`, and `teams_orgs`.

* `soft_delete` flags are respected across all entities — no physical deletion unless explicitly stated.

* Channel, chat, and file visibility determined by membership and ACLs.

* Private data (emails, messages) cannot be exposed via list APIs without filters.

---

## **Free-Form Text & Naming Conventions**

| Field           | Limit    | Format / Example                    |

| -------------------------- | ----------- | ------------------------------------------------------- |

| `displayName`       | 1–256 chars | "Project Phoenix – Engineering"             |

| `description`       | ≤1024 chars | "Internal collaboration space for release coordination" |

| `chatMessage.body.content` | ≤5000 chars | Rich text (HTML or plain)                |

| `tag.displayName`     | ≤40 chars  | Must be unique per team                 |

| `team.displayName`     | ≤255 chars | No reserved keywords (e.g., "General", "Admin")     |

---

## **Enumerations (Strict Values)**

### Teams & Channels

* `team.visibility`: `private`, `public`

* `channel.membershipType`: `standard`, `private`, `shared`

* `channelMessage.importance`: `normal`, `high`, `urgent`

### Chats

* `chat.chatType`: `oneOnOne`, `group`

* `chatMessage.messageType`: `message`, `chatEvent`, `systemEventMessage`

### Meetings

* `meeting.allowMeetingChat`: `enabled`, `disabled`

* `meeting.allowedPresenters`: `everyone`, `organizer`, `none`

### Virtual Events

* `audience`: `everyone`, `organization`, `unknownFutureValue`

* `status`: `draft`, `published`, `canceled`

### Presence

* `availability`: `Available`, `Busy`, `DoNotDisturb`, `Away`, `Offline`

* `activity`: `InMeeting`, `Available`, `Presenting`, `Away`, `BeRightBack`

---

## **Audit & Logging Requirements**

Every operation must record:

* `org_id`, `user_id`, and timestamp.

* `resource_id` and `operation_type`.

* System must update `updated_at` fields on every modification.

* Retain audit logs for ≥ 30 days for compliance.

---

## **Service-Level Policies**

* API rate limits per Microsoft Graph standards (429 handling).

* Call records, transcripts, and meeting data retained max **30 days**.

* Archived channels and teams are read-only.

* Bots may only perform operations within granted permissions (`Chat.ReadWrite`, `Team.ReadBasic.All`, etc.).

---

## **Violation Handling**

If an operation:

* Modifies unrelated entities,

* References non-existent IDs,

* Violates permission hierarchy,

* Or attempts disallowed state transitions,

the agent must **abort immediately** and return a policy violation notice.

---

Task:
I need to set up a centralized incident response chat for our team TechCorp Solutions. Create a group chat called 'Incident Response Triage' with John Davis, Alice Johnson, and Bob Smith. Post a kickoff message explaining this is now our hub for all P1 and P2 production issues. Pin it so it stays visible. Add a Planner tab for tracking follow-up tasks and a OneNote tab called 'Incident Post-Mortems' for documenting lessons learned. Once it's ready, start a call to walk everyone through the new workflow. After the group call, I need a quick one-on-one with Bob to discuss his incident lead responsibilities. Share our TechCorp Solutions Team member list in the chat so they know who to loop in for incidents. Finally, create an 'Incident Responders' tag in the team with John, Alice and Bob, and post our escalation procedure: P1 issues escalate to Mike Thompson after 15 minutes, P2 after 30 minutes.

Available tools:
list_users
add_tab_to_chat
list_teams
create_chat
list_teams_apps
list_team_members
create_call
send_chat_message
create_teamwork_tag
pin_chat_message

Verification checks:
[{"verifier_type": "database_state", "name": "techcorp_incident_responders_tag_created", "description": "Verify that the 'Incident Responders' teamwork tag was created on the TechCorp Solutions Team.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM teamwork_tags tt WHERE tt.team_id = 'team_techcorp_001' AND tt.display_name = 'Incident Responders';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_triage_chat_created_with_members", "description": "Verify that the 'Incident Response Triage' group chat exists and includes James Wilson, John Davis, Alice Johnson, and Bob Smith as members.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(DISTINCT cm.user_id) = 4 THEN 1 ELSE 0 END FROM chats ch JOIN chat_members cm ON ch.chat_id = cm.chat_id WHERE ch.topic = 'Incident Response Triage' AND ch.chat_type = 'group' AND cm.user_id IN ('james.wilson','john.davis','alice.johnson','bob.smith');", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_triage_kickoff_message_posted", "description": "Verify that a kickoff message was posted in the 'Incident Response Triage' chat describing P1/P2 usage and referencing Planner and OneNote.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM chats ch JOIN chat_messages m ON ch.chat_id = m.chat_id WHERE ch.topic = 'Incident Response Triage' AND LOWER(m.body_json) LIKE '%welcome%' AND LOWER(m.body_json) LIKE '%p1 and p2%' AND LOWER(m.body_json) LIKE '%planner tab%' AND LOWER(m.body_json) LIKE '%onenote tab%';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_triage_kickoff_message_pinned", "description": "Verify that the kickoff message in the 'Incident Response Triage' chat was pinned.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM chats ch JOIN chat_messages m ON ch.chat_id = m.chat_id JOIN pinned_chat_messages pcm ON pcm.chat_id = ch.chat_id AND pcm.message_id = m.message_id WHERE ch.topic = 'Incident Response Triage' AND LOWER(m.body_json) LIKE '%welcome to incident response triage%';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_triage_team_member_list_message_posted", "description": "Verify that a message was posted in the 'Incident Response Triage' chat listing the TechCorp Solutions Team members with their emails.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM chats ch JOIN chat_messages m ON ch.chat_id = m.chat_id WHERE ch.topic = 'Incident Response Triage' AND LOWER(m.body_json) LIKE '%team%' AND LOWER(m.body_json) LIKE '%james.wilson@techcorp.com%' AND LOWER(m.body_json) LIKE '%alice.manager@techcorp.com%' AND LOWER(m.body_json) LIKE '%bob.smith@techcorp.com%' AND LOWER(m.body_json) LIKE '%carol.white@techcorp.com%' AND LOWER(m.body_json) LIKE '%dave.brown@techcorp.com%';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_triage_escalation_message_posted", "description": "Verify that the escalation procedure message (P1/P2 timelines and Mike Thompson escalation) was posted in the 'Incident Response Triage' chat.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM chats ch JOIN chat_messages m ON ch.chat_id = m.chat_id WHERE ch.topic = 'Incident Response Triage' AND LOWER(m.body_json) LIKE '%escalation procedure%' AND LOWER(m.body_json) LIKE '%p1%' AND LOWER(m.body_json) LIKE '%p2%' AND LOWER(m.body_json) LIKE '%15 minutes%' AND LOWER(m.body_json) LIKE '%30 minutes%' AND LOWER(m.body_json) LIKE '%mike thompson%' AND LOWER(m.body_json) LIKE '%it.support@techcorp.com%';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_group_call_created_with_correct_participants", "description": "Verify that the group walkthrough call exists with James Wilson as source and John Davis, Alice Johnson, Bob Smith as targets.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM calls WHERE subject = 'Incident Response System Walkthrough' AND callback_uri = 'https://meetings.techcorp.com/api/calls' AND source LIKE '%james.wilson%' AND targets LIKE '%john.davis%' AND targets LIKE '%alice.johnson%' AND targets LIKE '%bob.smith%';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "techcorp_incident_one_on_one_call_with_bob_created", "description": "Verify that the one-on-one call with Bob Smith exists with James Wilson as source and Bob Smith as the only target.", "gym_name": "gym-teams-mcp", "validation_config": {"query": "SELECT CASE WHEN COUNT(*) > 0 THEN 1 ELSE 0 END FROM calls WHERE subject = 'Quick Sync - Incident Response' AND callback_uri = 'https://meetings.techcorp.com/api/calls' AND source LIKE '%james.wilson%' AND targets LIKE '%bob.smith%';", "expected_value": 1, "comparison_type": "equals"}}]