AI agents invoke stop_stack to trigger actions in Komodo MCP Server. 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.
Stopping a running stack is an Execute action—it runs a command/operation against external infrastructure whose effects depend on which stack is targeted. It is not Destructive because the stack can be restarted (reversible); it is not Financial (no money moved); it is not Write (does not create/modify data, but controls state).
From the tool's definition Tool name 'stop_stack' and description 'Detiene un stack en ejecución' (Stops a running stack) indicate the tool triggers an external operation that halts infrastructure. This is a control action on live systems with immediate operational consequences.
Documented attack patterns abuse exactly the kind of access stop_stack gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_stack:
{
"version": "1",
"default": "deny",
"tools": {
"stop_stack": {
"limits": [
{
"counter": "stop_stack_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_stack 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.
Detiene un stack en ejecución. It is categorised as a Execute tool in the Komodo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Komodo MCP Server MCP server in PolicyLayer and add a rule for stop_stack: 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 MCP Server. Nothing to install.
stop_stack 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_stack 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_stack. 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_stack is provided by the Komodo MCP Server MCP server (nonetss/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Komodo MCP Server, 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.
54 Komodo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.