zoom_list_recordings
Lists Zoom meeting recordings saved locally on this Mac (~/Documents/Zoom), newest first: meeting name, date, and which artifacts exist (transcript, captions, saved chat, audio, video). Local recordings only — no Zoom API, no admin approval. Use zoom_read_transcript to read the text of a meeting.
This record as markdown: /tools/com-local-mcp-local-mcp/zoom-list-recordings.md
What zoom_list_recordings does on Local
AI agents call zoom_list_recordings 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 |
|---|---|---|---|
limit | integer | — | Max recordings to return (default 20) |
Parameters from the server's own tool schema.
Why zoom_list_recordings is rated Low
This tool retrieves and queries locally stored Zoom recording metadata (names, dates, artifact types) with no side effects. It does not modify, execute code, delete, or move money. It is purely informational enumeration of existing recordings on the user's own system. Severity is low because it only surfaces information already accessible to the user via file system browsing, with no destructive or financial impact.
From the tool's definition Lists Zoom meeting recordings saved locally on this Mac (~/Documents/Zoom), newest first: meeting name, date, and which artifacts exist (transcript, captions, saved chat, audio, video). Local recordings only.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs zoom_list_recordings 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_list_recordings, this is the rule to start with:
zoom_list_recordings 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_list_recordings call is checked against it from then on.
Questions about zoom_list_recordings
Lists Zoom meeting recordings saved locally on this Mac (~/Documents/Zoom), newest first: meeting name, date, and which artifacts exist (transcript, captions, saved chat, audio, video). Local recordings only — no Zoom API, no admin approval. Use zoom_read_transcript to read the text of a meeting. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
zoom_list_recordings accepts 1 parameter: limit. 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_list_recordings: 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_list_recordings 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_list_recordings 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_list_recordings. 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_list_recordings 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