AI agents call get_current_user to retrieve information from Teams without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries user profile data. It has no side effects, cannot modify or delete data, and poses minimal risk. The blast radius of misuse is very limited — an agent could learn the authenticated user's identity, but this is typically non-sensitive metadata and the operation itself is benign.
From the tool's definition Tool name is 'get_current_user' and description states 'Get the current authenticated user' — this retrieves user identity information without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get the current authenticated user. It is categorised as a Read tool in the Teams MCP Server, which means it retrieves data without modifying state.
Register the Teams MCP server in PolicyLayer and add a rule for get_current_user: 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. Nothing to install.
get_current_user 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 get_current_user 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 get_current_user. 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.
get_current_user is provided by the Teams MCP server (@floriscornel/teams-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.