26 tools. 16 can modify or destroy data without limits.
5 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (delete-container-registry-auth, delete-endpoint, delete-network-volume) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (create-container-registry-auth, create-endpoint, create-network-volume) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (start-pod, stop-pod) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and RunPod. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @runpod/runpod-mcp-ts delete-container-registry-auth:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
create-container-registry-auth:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
get-container-registry-auth:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The RunPod server exposes 5 destructive tools including delete-container-registry-auth, delete-endpoint, delete-network-volume. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The RunPod server has 9 write tools including create-container-registry-auth, create-endpoint, create-network-volume. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
26 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 16 can modify, create, or delete data.
One line change. Instead of running the RunPod server directly, prefix it with Intercept: intercept -c runpod-runpod-mcp-ts.yaml -- npx -y @runpod/runpod-mcp-ts. Download a pre-built policy from policylayer.com/policies/runpod-runpod-mcp-ts and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init