Retrieve the cleaned transcript for a Microsoft Teams meeting.
AI agents call get_meeting_transcript to retrieve information from Transcripts 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 meeting transcript data from Microsoft Teams via the Microsoft Graph API. It performs a read-only query operation with no side effects—the transcript already exists and is merely being fetched for the AI agent to analyze.
From the tool's definition Tool description states 'Retrieve the cleaned transcript' - a retrieval operation with no modification, creation, or deletion of data.
Documented attack patterns abuse exactly the kind of access get_meeting_transcript gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Transcripts MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_meeting_transcript:
{
"version": "1",
"default": "deny",
"tools": {
"get_meeting_transcript": {}
}
}get_meeting_transcript is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the cleaned transcript for a Microsoft Teams meeting. It is categorised as a Read tool in the Transcripts MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Transcripts MCP Server MCP server in PolicyLayer and add a rule for get_meeting_transcript: 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 Transcripts MCP Server. Nothing to install.
get_meeting_transcript 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_meeting_transcript 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_meeting_transcript. 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_meeting_transcript is provided by the Transcripts MCP Server MCP server (itspecialist111/microsoftgraph_transcript_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Transcripts MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Transcripts MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.