AI agents call get_procedure 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.
The 'get_' prefix strongly suggests a read-only retrieval operation. With no description, confidence is moderated, but the naming convention and absence of action verbs like 'create', 'delete', or 'execute' indicate this fetches procedure data rather than executing procedures or modifying resources.
From the tool's definition Tool name 'get_procedure' follows retrieval pattern (get_*); no description provided. In context of Komodo DevOps platform, 'get' operations typically retrieve procedure definitions without modification.
Documented attack patterns abuse exactly the kind of access get_procedure 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 get_procedure:
{
"version": "1",
"default": "deny",
"tools": {
"get_procedure": {}
}
}get_procedure 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.
get_procedure. 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 get_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. Nothing to install.
get_procedure 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 get_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 get_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.
get_procedure 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.