runtime_stop_application · Anypoint MCP Server MCP

WHAT IT DOES

What runtime_stop_application does on Anypoint MCP Server

AI agents invoke runtime_stop_application to trigger actions in Anypoint MCP Server. 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 runtime_stop_application needs a policy

Stopping a running application is an Execute action—it triggers an external operation (application shutdown) whose effects depend on which application is targeted via deploymentId. While not destructive (the application and data persist; it can be restarted), it is not reversible in real-time and disrupts service availability.

From the tool's definition Tool name 'runtime_stop_application' and description 'Stop a running Runtime Manager application' indicate execution of an operational command that terminates a live application.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

runtime_stop_application Rate-limited

runtime_stop_application 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": {
    "runtime_stop_application": {
      "limits": [
        {
          "counter": "runtime_stop_application_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 Anypoint MCP Server, so you can run agents against it safely.

FAQ

Questions about runtime_stop_application

What does the runtime_stop_application tool do? +

Stop a running Runtime Manager application. Call runtime_list_deployments first to obtain the deploymentId. It is categorised as a Execute tool in the Anypoint MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on runtime_stop_application? +

Register the Anypoint MCP Server MCP server in PolicyLayer and add a rule for runtime_stop_application: 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_stop_application? +

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

Can I rate-limit runtime_stop_application? +

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

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

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