runtime_update_deployment · Anypoint MCP Server MCP

WHAT IT DOES

What runtime_update_deployment does on Anypoint MCP Server

AI agents use runtime_update_deployment to create or update resources in Anypoint MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Anypoint MCP Server environment.

WHY IT NEEDS A POLICY

Why runtime_update_deployment needs a policy

This tool modifies (patches) deployment configuration in Runtime Manager, making it a Write operation that creates or modifies data reversibly. While patching deployments could have operational side effects, it is not irreversible (configurations can be re-patched) and does not delete data, so it does not qualify as Destructive.

From the tool's definition Tool name 'runtime_update_deployment' and description 'Patch a Runtime Manager deployment configuration' indicate modification of existing deployment settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runtime_update_deployment Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "runtime_update_deployment": {
      "limits": [
        {
          "counter": "runtime_update_deployment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about runtime_update_deployment

What does the runtime_update_deployment tool do? +

Patch a Runtime Manager deployment configuration. Requires ANYPOINT_MCP_ADVANCED_TOOLS=true. It is categorised as a Write tool in the Anypoint MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on runtime_update_deployment? +

Register the Anypoint MCP Server MCP server in PolicyLayer and add a rule for runtime_update_deployment: 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 Anypoint MCP Server. Nothing to install.

What risk level is runtime_update_deployment? +

runtime_update_deployment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit runtime_update_deployment? +

Yes. Add a rate_limit block to the runtime_update_deployment 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 runtime_update_deployment completely? +

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

runtime_update_deployment is provided by the Anypoint MCP Server MCP server (sravannerella/mulesoft-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.