Read recent messages from a direct or group chat. Use teams_list_chats first to get the chat ID.
AI agents call teams_read_chat_messages to retrieve information from Microsoft Teams without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves chat message history with no side effects. It is purely informational and matches the 'Read' category definition (retrieves or queries data; no side effects). Severity is low because exposure is limited to message history that the authenticated user already has access to in Teams, with no ability to alter state or trigger external actions.
From the tool's definition Tool name and description explicitly state 'Read recent messages from a direct or group chat.' No modification, deletion, or execution capability is described.
Attacks that exploit this kind of access
Read recent messages from a direct or group chat. Use teams_list_chats first to get the chat ID. It is categorised as a Read tool in the Microsoft Teams MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Teams MCP server in PolicyLayer and add a rule for teams_read_chat_messages: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Microsoft Teams. Nothing to install.
teams_read_chat_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the teams_read_chat_messages rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for teams_read_chat_messages. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
teams_read_chat_messages is provided by the Microsoft Teams MCP server (microsoft-teams-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →