AI agents use update_build to create or update resources in Komodo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Komodo MCP Server environment.
This tool modifies build configurations reversibly without permanently deleting resources or executing arbitrary code. It qualifies as Write rather than Execute because it changes configuration data rather than triggering build execution.
From the tool's definition Tool name 'update_build' and description 'Actualiza la configuración de un build existente' (Updates the configuration of an existing build) indicates modification of existing build configurations.
Documented attack patterns abuse exactly the kind of access update_build 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 update_build:
{
"version": "1",
"default": "deny",
"tools": {
"update_build": {
"limits": [
{
"counter": "update_build_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_build 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.
Actualiza la configuración de un build existente. It is categorised as a Write tool in the Komodo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Komodo MCP Server MCP server in PolicyLayer and add a rule for update_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 MCP Server. Nothing to install.
update_build 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_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 update_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.
update_build 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.