deploy_registry_codebundle · RunWhen Platform MCP

WHAT IT DOES

What deploy_registry_codebundle does on RunWhen Platform MCP

AI agents invoke deploy_registry_codebundle to trigger actions in RunWhen Platform MCP. 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.

WHY IT NEEDS A POLICY

Why deploy_registry_codebundle needs a policy

The tool performs a deployment action—pushing code to a registry—which is an external operation that executes and has real-world consequences. While the description is empty (reducing confidence slightly), the name strongly suggests Execute-category behavior (triggering deployment automation).

From the tool's definition Tool name 'deploy_registry_codebundle' indicates deployment of code bundles to a registry, which triggers external operations with effects dependent on the bundle contents.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_registry_codebundle Rate-limited

deploy_registry_codebundle 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_registry_codebundle": {
      "limits": [
        {
          "counter": "deploy_registry_codebundle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RunWhen Platform MCP, so you can run agents against it safely.

FAQ

Questions about deploy_registry_codebundle

What does the deploy_registry_codebundle tool do? +

deploy_registry_codebundle. It is categorised as a Execute tool in the RunWhen Platform MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on deploy_registry_codebundle? +

Register the RunWhen Platform MCP server in PolicyLayer and add a rule for deploy_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.

What risk level is deploy_registry_codebundle? +

deploy_registry_codebundle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_registry_codebundle? +

Yes. Add a rate_limit block to the deploy_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.

How do I block deploy_registry_codebundle completely? +

Set action: deny in the PolicyLayer policy for deploy_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.

What MCP server provides deploy_registry_codebundle? +

deploy_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.