Search for messages in Microsoft Teams. Returns matching messages with sender, timestamp, content, conversationId (for replies), and pagination info. Supports operators: from:email, to:name, sent:YYYY-MM-DD, sent:today, is:Messages, is:Meetings, is:Channels, is:Chats, hasattachment:true,
AI agents call teams_search to retrieve information from Teams MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries message data without any side effects. It does not create, modify, delete, or execute anything—it only searches and returns results. This is a classic Read operation with minimal security risk even if abused, as it only exposes existing messages the user would typically have access to view anyway.
From the tool's definition Tool description states it 'Search for messages in Microsoft Teams. Returns matching messages' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search for messages in Microsoft Teams. Returns matching messages with sender, timestamp, content, conversationId (for replies), and pagination info. Supports operators: from:email, to:name, sent:YYYY-MM-DD, sent:today, is:Messages, is:Meetings, is:Channels, is:Chats, hasattachment:true,. It is categorised as a Read tool in the Teams MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Teams MCP Server MCP server in PolicyLayer and add a rule for teams_search: 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 Teams MCP Server. Nothing to install.
teams_search 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_search 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_search. 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_search is provided by the Teams MCP Server MCP server (m0nkmaster/msteams-mcp). 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 →