get-container-registry-auth
AI agents call get-container-registry-auth to retrieve information from RunPod MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored container registry authentication data without modifying or deleting it. While it accesses sensitive credentials, the tool itself performs only a read operation. The severity is low because merely retrieving auth credentials does not directly enable unauthorized operations—misuse would require separately using those credentials elsewhere.
From the tool's definition Tool name 'get-container-registry-auth' indicates retrieval of authentication credentials for container registries.
Attacks that exploit this kind of access
get-container-registry-auth. It is categorised as a Read tool in the RunPod MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for get-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.
get-container-registry-auth is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-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.
Set action: deny in the PolicyLayer policy for get-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.
get-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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →