List recent Microsoft Teams online meetings for the signed-in user.
AI agents call list_recent_meetings 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 performs a read-only operation that queries meeting metadata (list of recent meetings) and returns data without side effects. No data is modified, deleted, or executed. The scope is limited to the authenticated user's own meetings, reducing blast radius. It is the least severe category of security risk.
From the tool's definition The tool 'list_recent_meetings' retrieves and lists Microsoft Teams meeting data for the signed-in user. The description explicitly states it 'List[s] recent Microsoft Teams online meetings' with no modification, deletion, or execution capabilities mentioned.
Documented attack patterns abuse exactly the kind of access list_recent_meetings 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 list_recent_meetings:
{
"version": "1",
"default": "deny",
"tools": {
"list_recent_meetings": {}
}
}list_recent_meetings 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.
List recent Microsoft Teams online meetings for the signed-in user. 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 list_recent_meetings: 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.
list_recent_meetings 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 list_recent_meetings 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 list_recent_meetings. 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.
list_recent_meetings 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.