AI agents call list_builds 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 build information without creating, modifying, executing, or deleting any resources. It is a straightforward read operation that poses minimal security risk if misused by an AI agent, as it only exposes existing build data.
From the tool's definition Tool name 'list_builds' and description 'List all builds in Komodo' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_builds 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_builds:
{
"version": "1",
"default": "deny",
"tools": {
"list_builds": {}
}
}list_builds 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 builds 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_builds: 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_builds 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_builds 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_builds. 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_builds 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.