Get the user\
AI agents call teams_get_frequent_contacts 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 contact data for the authenticated user. It performs a query operation without side effects—no data is created, modified, deleted, or used to trigger external actions. The incomplete description ('Get the user\') suggests it fetches frequently contacted users, which is a read operation.
From the tool's definition Tool name 'teams_get_frequent_contacts' and description pattern consistent with retrieval operation ('Get the user...'). No modification, deletion, or execution of external processes indicated.
Attacks that exploit this kind of access
Get the user\. 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_get_frequent_contacts: 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_get_frequent_contacts 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_get_frequent_contacts 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_get_frequent_contacts. 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_get_frequent_contacts 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 →