stop_encoder
Stop an Encoder. Destructive - requires confirm: true in safe mode.
This record as markdown: /tools/com-zype-mcp-server/stop-encoder.md
What stop_encoder does on Zype Com
AI agents invoke stop_encoder 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 |
|---|---|---|---|
body | object | — | Request body fields |
confirm | boolean | — | Set true to confirm (required in safe mode) |
encoder_name | string | Yes | encoder_name (required) |
Parameters from the server's own tool schema.
Why stop_encoder is rated High
stop_encoder 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 stop_encoder 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 stop_encoder, this is the rule to start with:
stop_encoder 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 stop_encoder call is checked against it from then on.
Questions about stop_encoder
Stop an Encoder. 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.
stop_encoder accepts 3 parameters: body, confirm, encoder_name. Required: encoder_name. 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 stop_encoder: 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.
stop_encoder 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 stop_encoder 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 stop_encoder. 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.
stop_encoder 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