stop-pod · RunPod MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop-pod does on RunPod MCP Server

AI agents invoke stop-pod to trigger actions in RunPod 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 stop-pod needs a policy

Stopping a pod is an Execute action—it triggers an external operation (pod termination) whose side effects depend on which pod is targeted. While not destructive (data persists), it interrupts active workloads and can cause service outages. The empty description reduces confidence slightly, but the clear intent from the tool name and RunPod API context is unambiguous.

From the tool's definition Tool name 'stop-pod' indicates termination of a running pod; the sibling tools 'create-pod' and 'delete-pod' confirm this server manages pod lifecycle operations. Stopping a pod halts a running computation/service.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop-pod Rate-limited

stop-pod 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": {
    "stop-pod": {
      "limits": [
        {
          "counter": "stop-pod_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 RunPod MCP Server, so you can run agents against it safely.

FAQ

Questions about stop-pod

What does the stop-pod tool do? +

stop-pod. It is categorised as a Execute tool in the RunPod 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 stop-pod? +

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

What risk level is stop-pod? +

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

Can I rate-limit stop-pod? +

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

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

stop-pod is provided by the RunPod MCP Server MCP server (niel-runpod/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.