get_registry_codebundle
AI agents call get_registry_codebundle to retrieve information from RunWhen Platform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly indicates a read/retrieval operation with no side effects. Despite the empty description lowering confidence slightly, the naming convention and context of similar tools on the server support classification as a Read operation with low severity—it retrieves a code bundle from the registry without modifying or executing it.
From the tool's definition Tool name 'get_registry_codebundle' indicates a retrieval operation (get prefix). No description provided to confirm scope, but sibling tools include read operations like 'get_assistant' and destructive operations like 'delete_slx', suggesting this follows…
Attacks that exploit this kind of access
get_registry_codebundle. It is categorised as a Read tool in the RunWhen Platform MCP MCP Server, which means it retrieves data without modifying state.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for get_registry_codebundle: 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 RunWhen Platform MCP. Nothing to install.
get_registry_codebundle 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_registry_codebundle 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_registry_codebundle. 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_registry_codebundle is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →