Search for people in Microsoft Teams by name or email. Returns matching users with display name, email, job title, and department. Useful for finding someone to message.
AI agents call teams_search_people 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 user information from Microsoft Teams without any side effects. It does not create, modify, delete, or execute actions—it only queries and returns user profile data. This is a straightforward read operation with minimal risk; exposure of the tool allows only discovery of existing public or internal directory information, not manipulation of Teams data or external operations.
From the tool's definition Tool description states it 'Search[es] for people in Microsoft Teams by name or email' and 'Returns matching users with display name, email, job title, and department.' The verb 'search' and 'returns' indicate data retrieval with no modification or deletion…
Attacks that exploit this kind of access
Search for people in Microsoft Teams by name or email. Returns matching users with display name, email, job title, and department. Useful for finding someone to message. 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_people: 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_people 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_people 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_people. 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_people 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 →