Get detailed information about a specific Zoom meeting recording including recording files and metadata
AI agents call zoom_get_recording_details to retrieve information from Zoom Recordings No-Auth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data about Zoom recordings (metadata and file information) without creating, modifying, or deleting records. It is a Read operation. Severity is medium rather than low because: (1) the server operates 'without requiring direct authentication from the end user' per the server description, suggesting potential unauthorized access risks; (2) Zoom recordings may contain sensitive meeting…
From the tool's definition Tool description states 'Get detailed information about a specific Zoom meeting recording including recording files and metadata'. The verb 'Get' and noun 'detailed information' indicate retrieval without modification.
Documented attack patterns abuse exactly the kind of access zoom_get_recording_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoom Recordings No-Auth, and nothing reaches the server without passing your rules. This is the rule we recommend for zoom_get_recording_details:
{
"version": "1",
"default": "deny",
"tools": {
"zoom_get_recording_details": {}
}
}zoom_get_recording_details 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.
Get detailed information about a specific Zoom meeting recording including recording files and metadata. It is categorised as a Read tool in the Zoom Recordings No-Auth MCP Server, which means it retrieves data without modifying state.
Register the Zoom Recordings No-Auth MCP server in PolicyLayer and add a rule for zoom_get_recording_details: 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 Zoom Recordings No-Auth. Nothing to install.
zoom_get_recording_details 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_get_recording_details 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_get_recording_details. 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_get_recording_details is provided by the Zoom Recordings No-Auth MCP server (peakmojo/mcp-server-zoom-noauth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoom Recordings No-Auth, 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.
4 Zoom Recordings No-Auth tools catalogued and risk-classified — across an index of 43,000+ MCP servers.