AI agents invoke stop_deployment to trigger actions in Komodo. 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.
Although the description is empty (lowering confidence slightly), the tool name and server context clearly indicate this performs an external operational action on deployed infrastructure. Stopping a deployment is an Execute action—it triggers a state change in running systems but is reversible (deployments can be restarted).
From the tool's definition Tool named 'stop_deployment' in komodo-mcp server context where sibling tools include create_deployment, create_build, create_server, create_stack.
Documented attack patterns abuse exactly the kind of access stop_deployment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_deployment:
{
"version": "1",
"default": "deny",
"tools": {
"stop_deployment": {
"limits": [
{
"counter": "stop_deployment_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_deployment 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.
Free to start. No card required.
stop_deployment. It is categorised as a Execute tool in the Komodo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Komodo MCP server in PolicyLayer and add a rule for stop_deployment: 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 Komodo. Nothing to install.
stop_deployment 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_deployment 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_deployment. 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_deployment is provided by the Komodo MCP server (myrikld/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo, 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.
53 Komodo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.