playout_stop_channel
Stop On-Air Channel. Playout Scheduler (Channels). Destructive - requires confirm: true in safe mode.
This record as markdown: /tools/com-zype-mcp-server/playout-stop-channel.md
What playout_stop_channel does on Zype Com
AI agents invoke playout_stop_channel to trigger actions in Zype Com. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | id (required) |
body | object | — | Request body fields for this operation |
confirm | boolean | — | Set true to confirm (required in safe mode) |
Parameters from the server's own tool schema.
Why playout_stop_channel is rated High
playout_stop_channel triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs playout_stop_channel 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_stop_channel, this is the rule to start with:
playout_stop_channel stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every playout_stop_channel call is checked against it from then on.
Questions about playout_stop_channel
Stop On-Air Channel. Playout Scheduler (Channels). Destructive - requires confirm: true in safe mode. It is categorised as a Execute tool in the Zype Com MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
playout_stop_channel accepts 3 parameters: id, body, confirm. Required: 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_stop_channel: 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_stop_channel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the playout_stop_channel 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_stop_channel. 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_stop_channel 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