Actualiza la configuración de un procedimiento existente
AI agents use update_procedure 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 existing procedure configurations in Komodo infrastructure. While reversible (Write rather than Destructive), it poses high severity because misconfigured procedures in an infrastructure management system could disrupt deployments, builds, or other critical operations.
From the tool's definition update_procedure: 'Actualiza la configuración de un procedimiento existente' (Updates the configuration of an existing procedure). The description explicitly indicates modification of existing infrastructure configuration.
Documented attack patterns abuse exactly the kind of access update_procedure 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_procedure:
{
"version": "1",
"default": "deny",
"tools": {
"update_procedure": {
"limits": [
{
"counter": "update_procedure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_procedure 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 procedimiento 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_procedure: 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_procedure 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_procedure 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_procedure. 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_procedure 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.