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

WHAT IT DOES

What update-pod does on RunPod MCP Server

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

WHY IT NEEDS A POLICY

Why update-pod needs a policy

Based on the pattern of sibling tools (create-pod, delete-pod) and the server's purpose of managing RunPod resources, update-pod modifies pod configuration or state reversibly. This is a Write action rather than Destructive (not deleting) or Execute (not running arbitrary commands).

From the tool's definition Tool is named 'update-pod' and exists on a RunPod management server that handles 'managing pods, endpoints, templates, network volumes, and container registry authentications.' The sibling tools include create-pod and delete-pod, contextualizing this as a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-pod Rate-limited

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

FAQ

Questions about update-pod

What does the update-pod tool do? +

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

Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for update-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 update-pod? +

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

Can I rate-limit update-pod? +

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

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

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