Get the list of threads the user is following in Teams. Returns references to followed threads with source conversation IDs and direct links. Use teams_get_message with sourceConversationId and sourcePostId to fetch the full post, or teams_get_thread for the full thread.
AI agents call teams_get_followed_threads 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 information about followed threads and returns references/links to them. It has no side effects, does not modify Teams data, and does not execute commands or trigger external operations. The only action is querying and returning existing data to the user. This is a classic Read category operation.
From the tool's definition Tool name is 'teams_get_followed_threads' and description states 'Get the list of threads the user is following' — a retrieval operation that returns read-only references and metadata without modifying any data.
Attacks that exploit this kind of access
Get the list of threads the user is following in Teams. Returns references to followed threads with source conversation IDs and direct links. Use teams_get_message with sourceConversationId and sourcePostId to fetch the full post, or teams_get_thread for the full thread. 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_followed_threads: 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_followed_threads 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_followed_threads 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_followed_threads. 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_followed_threads 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 →