AI agents call delete_a_meeting to permanently remove resources in Zoom MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a meeting record via the Zoom API. Once deleted, the meeting cannot be recovered through normal means. The action cannot be undone. This is a classic Destructive operation (delete semantics). Severity is high because deleting a meeting affects all attendees who may have scheduled time around it, but the blast radius is limited to a single meeting (not system-wide).
From the tool's definition Tool name 'delete_a_meeting' and description 'Delete a meeting with a given ID' explicitly indicate irreversible deletion of a meeting resource.
Documented attack patterns abuse exactly the kind of access delete_a_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_a_meeting:
{
"version": "1",
"default": "deny",
"hide": [
"delete_a_meeting"
]
}delete_a_meeting disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a meeting with a given ID. It is categorised as a Destructive tool in the Zoom MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zoom MCP Server MCP server in PolicyLayer and add a rule for delete_a_meeting: 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 MCP Server. Nothing to install.
delete_a_meeting is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_a_meeting 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 delete_a_meeting. 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.
delete_a_meeting is provided by the Zoom MCP Server MCP server (javaprogrammerlb/zoom-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoom 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.
4 Zoom MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.