AI agents use update_stack to create or update resources in Komodo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Komodo environment.
The verb 'update' indicates modification of existing data, which is reversible. Without a description, confidence is reduced from high. However, updating infrastructure stacks (e.g., Kubernetes, Docker Compose) in a DevOps platform could have moderate blast radius if an agent makes incorrect changes to production stacks, warranting 'medium' severity.
From the tool's definition Tool name is 'update_stack' with no description provided. Based on the server's purpose (managing Komodo DevOps platform resources) and the presence of sibling create/delete operations, this tool modifies existing stack configurations.
Documented attack patterns abuse exactly the kind of access update_stack 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 update_stack:
{
"version": "1",
"default": "deny",
"tools": {
"update_stack": {
"limits": [
{
"counter": "update_stack_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_stack stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_stack. It is categorised as a Write tool in the Komodo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Komodo MCP server in PolicyLayer and add a rule for update_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. Nothing to install.
update_stack is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_stack 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.