Run a build (clone repo, build Docker image, push to registry).
AI agents invoke run_build 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.
This tool triggers code execution (cloning, building Docker images) and pushes artifacts to external registries. While not destructive on its own, it executes complex operations whose side effects (image creation, registry mutations, potential resource consumption) are determined by user input. This falls squarely in the Execute category.
From the tool's definition The tool description states it 'Run[s] a build (clone repo, build Docker image, push to registry)' — this executes a multi-step build pipeline including cloning repositories, building Docker images, and pushing to registries, which are external operations…
Documented attack patterns abuse exactly the kind of access run_build 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 run_build:
{
"version": "1",
"default": "deny",
"tools": {
"run_build": {
"limits": [
{
"counter": "run_build_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_build 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.
Run a build (clone repo, build Docker image, push to registry). 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 run_build: 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.
run_build 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 run_build 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 run_build. 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.
run_build 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.