playout_delete_destination
Delete Destination. Playout Scheduler (Destinations). Destructive - requires confirm: true in safe mode.
This record as markdown: /tools/com-zype-mcp-server/playout-delete-destination.md
What playout_delete_destination does on Zype Com
AI agents call playout_delete_destination to permanently remove resources in Zype Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | id (required) |
confirm | boolean | — | Set true to confirm (required in safe mode) |
destination_id | string | Yes | destinationId (required) |
Parameters from the server's own tool schema.
Why playout_delete_destination is rated Critical
An AI agent that decides to call playout_delete_destination doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Zype Com is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs playout_delete_destination safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For playout_delete_destination, this is the rule to start with:
playout_delete_destination 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 Zype Com, apply this rule, and every playout_delete_destination call is checked against it from then on.
Questions about playout_delete_destination
Delete Destination. Playout Scheduler (Destinations). Destructive - requires confirm: true in safe mode. It is categorised as a Destructive tool in the Zype Com MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
playout_delete_destination accepts 3 parameters: id, confirm, destination_id. Required: id, destination_id. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for playout_delete_destination: 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 Zype Com. Nothing to install.
playout_delete_destination 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 playout_delete_destination 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 playout_delete_destination. 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.
playout_delete_destination is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
Across the catalogue