Get files and links shared in a Teams conversation. Returns file names, URLs, extensions, sizes, and who shared them. Works for channels, group chats, 1:1 chats, and meeting chats. Use the conversationId from other tools (teams_get_favorites, teams_search, teams_find_channel, teams_get_chat). Sup...
AI agents call teams_get_shared_files 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 existing data (file metadata and sharing information) from Teams conversations without creating, modifying, deleting, or executing any operations. It has no side effects and is purely informational. While it could expose sensitive file information, the blast radius is limited to data exposure rather than system compromise or action execution.
From the tool's definition Tool description states it 'Get files and links shared in a Teams conversation' and 'Returns file names, URLs, extensions, sizes, and who shared them.' The verb 'Get' and the retrieval-only nature of returning metadata without modification indicate a read…
Attacks that exploit this kind of access
Get files and links shared in a Teams conversation. Returns file names, URLs, extensions, sizes, and who shared them. Works for channels, group chats, 1:1 chats, and meeting chats. Use the conversationId from other tools (teams_get_favorites, teams_search, teams_find_channel, teams_get_chat). Supports pagination via skipToken for conversations with many files. 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_shared_files: 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_shared_files 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_shared_files 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_shared_files. 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_shared_files 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 →