zoom_read_transcript
Reads the text artifacts of a local Zoom recording: the transcript/captions (.vtt or closed_caption.txt, cleaned to readable 'Speaker: text' lines) and the saved in-meeting chat. Pass the recording name or path from zoom_list_recordings. Perfect for 'summarize my last meeting' or 'what did we agr...
This record as markdown: /tools/com-local-mcp-local-mcp/zoom-read-transcript.md
What zoom_read_transcript does on Local
AI agents call zoom_read_transcript to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
include | string | — | 'all' (default), 'transcript' or 'chat' |
recording | string | Yes | Recording folder name (or full path) from zoom_list_recordings. Partial name match works. |
Parameters from the server's own tool schema.
Why zoom_read_transcript is rated Low
This tool retrieves and returns existing transcript and chat data from local Zoom recordings without modifying, executing code, deleting, or performing financial operations. It has no side effects beyond reading. The use cases given ('summarize my last meeting', 'what did we agree on') are purely informational queries.
From the tool's definition Tool description states it 'Reads the text artifacts of a local Zoom recording: the transcript/captions...and the saved in-meeting chat.' The verb 'reads' and the passive voice 'captions (cleaned to readable...)' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs zoom_read_transcript safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_read_transcript, this is the rule to start with:
zoom_read_transcript is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every zoom_read_transcript call is checked against it from then on.
Questions about zoom_read_transcript
Reads the text artifacts of a local Zoom recording: the transcript/captions (.vtt or closed_caption.txt, cleaned to readable 'Speaker: text' lines) and the saved in-meeting chat. Pass the recording name or path from zoom_list_recordings. Perfect for 'summarize my last meeting' or 'what did we agree on in the kickoff call'. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
zoom_read_transcript accepts 2 parameters: include, recording. Required: recording. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for zoom_read_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 Local. Nothing to install.
zoom_read_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 zoom_read_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 zoom_read_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.
zoom_read_transcript is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue