This record as markdown: /tools/sagemcp-sagemcp/zoom-delete-meeting.md
What zoom_delete_meeting does on Sage MCP
AI agents call zoom_delete_meeting to permanently remove resources in Sage MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why zoom_delete_meeting is rated Critical
Deleting a meeting is an irreversible action that cannot be undone. Once deleted, the meeting schedule is gone and cannot be recovered through normal means. This matches the 'Destructive' category definition (irreversibly deletes or overwrites data, or actions that cannot be undone).
From the tool's definition The tool is named 'zoom_delete_meeting' with description 'Delete a scheduled meeting'. The verb 'delete' is explicitly destructive—it removes a meeting irreversibly.
Attacks that exploit this kind of access
The rule that runs zoom_delete_meeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_delete_meeting, this is the rule to start with:
zoom_delete_meeting is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every zoom_delete_meeting call is checked against it from then on.
Questions about zoom_delete_meeting
Delete a scheduled meeting. It is categorised as a Destructive tool in the Sage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sage MCP server in PolicyLayer and add a rule for zoom_delete_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 Sage MCP. Nothing to install.
zoom_delete_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 zoom_delete_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 zoom_delete_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.
zoom_delete_meeting is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
Across the catalogue