create-container-registry-auth

THE RISK

Medium Risk

Why create-container-registry-auth needs a policy

The 'create' action indicates data modification (likely creating authentication credentials or entries in a container registry). This is a Write-category operation rather than Destructive because creation is typically reversible (credentials can be deleted).

From the tool's definition Tool name is 'create-container-registry-auth', which performs a create operation. The description is empty, limiting direct assessment of its scope and reversibility.

Documented attack patterns abuse exactly the kind of access create-container-registry-auth gives an agent:

POLICY

How to control create-container-registry-auth

PolicyLayer is an MCP gateway — it sits between your AI agents and Novita MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-container-registry-auth:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-container-registry-auth": {
      "limits": [
        {
          "counter": "create-container-registry-auth_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register Novita MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Novita MCP Server tools

Destructive delete-container-registry-auth delete-container-registry-auth Destructive delete-gpu-instance delete-gpu-instance Destructive delete-network-storage delete-network-storage Destructive delete-template delete-template Execute restart-gpu-instance restart-gpu-instance Execute start-gpu-instance start-gpu-instance Execute stop-gpu-instance stop-gpu-instance Write create-gpu-instance create-gpu-instance

All 20 Novita MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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 Novita 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 Novita 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 Novita 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 Novita MCP Server MCP server (novitalabs/novita-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Novita MCP Server tool call.

Start from Novita MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →