create-container-registry-auth · RunPod MCP Server MCP

WHAT IT DOES

What create-container-registry-auth does on RunPod MCP Server

AI agents use create-container-registry-auth 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 create-container-registry-auth needs a policy

This tool creates new authentication records for container registries, which is a Write operation (reversible via the delete-container-registry-auth counterpart). The severity is medium because misuse could expose or misconfigure registry credentials, potentially allowing unauthorized access to private container images, but the actual credential exposure depends on how the tool handles secrets.

From the tool's definition Tool name 'create-container-registry-auth' indicates creation of authentication credentials for container registries. Sibling tools include 'delete-container-registry-auth', confirming this tool creates reversible records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-container-registry-auth Rate-limited

create-container-registry-auth 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": {
    "create-container-registry-auth": {
      "limits": [
        {
          "counter": "create-container-registry-auth_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 create-container-registry-auth

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

create-container-registry-auth. 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 create-container-registry-auth? +

Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for create-container-registry-auth: 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 create-container-registry-auth? +

create-container-registry-auth is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

Yes. Add a rate_limit block to the create-container-registry-auth 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 create-container-registry-auth completely? +

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

create-container-registry-auth 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.