delete-container-registry-auth

// WHEN AI AGENTS USE THIS TOOL

AI agents may call delete-container-registry-auth to permanently remove or destroy resources in RunPod. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON DELETE-CONTAINER-REGISTRY-AUTH

Without a policy, an AI agent could call delete-container-registry-auth in a loop, permanently destroying resources in RunPod. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

runpod-runpod-mcp-ts.yaml

tools:
  delete-container-registry-auth:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full RunPod policy for all 26 tools.

// DETAILS

Tool Name delete-container-registry-auth

Category Destructive

MCP Server RunPod MCP Server

Risk Level Critical

// MORE RUNPOD TOOLS

Destructive delete-endpoint Destructive delete-network-volume Destructive delete-pod Destructive delete-template Execute start-pod Execute stop-pod Write create-container-registry-auth Write create-endpoint

View all 26 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like delete-container-registry-auth have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete Agent Passport System — Cryptographic Identity for AI Agents remove_intent_card Agent Passport System — Cryptographic Identity for AI Agents revoke_delegation

// IN CONTEXT OF CRITICAL RISK

delete-container-registry-auth is one of the critical-risk operations in RunPod. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the delete-container-registry-auth tool do? +

delete-container-registry-auth. It is categorised as a Destructive tool in the RunPod MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-container-registry-auth? +

Add a rule in your Intercept YAML policy under the tools section for delete-container-registry-auth. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the RunPod MCP server.

What risk level is delete-container-registry-auth? +

delete-container-registry-auth is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-container-registry-auth? +

Yes. Add a rate_limit block to the delete-container-registry-auth rule in your Intercept 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 delete-container-registry-auth completely? +

Set action: deny in the Intercept policy for delete-container-registry-auth. 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 delete-container-registry-auth? +

delete-container-registry-auth is provided by the RunPod MCP server (runpod/runpod-mcp-ts). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on RunPod