AI agents call list_stacks to retrieve information from Komodo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing stacks without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk, as it only exposes stack metadata/inventory that an authorized user would expect to access. Severity is low because listing stacks does not inherently enable malicious actions—it is purely informational.
From the tool's definition Tool name 'list_stacks' and description 'List all stacks in Komodo' indicate a retrieval operation with no modification or execution side effects.
Documented attack patterns abuse exactly the kind of access list_stacks 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 list_stacks:
{
"version": "1",
"default": "deny",
"tools": {
"list_stacks": {}
}
}list_stacks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all stacks in Komodo. It is categorised as a Read tool in the Komodo MCP Server, which means it retrieves data without modifying state.
Register the Komodo MCP server in PolicyLayer and add a rule for list_stacks: 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.
list_stacks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_stacks 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 list_stacks. 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.
list_stacks 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.