rename_container · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_container does on Docker MCP Server

AI agents use rename_container to create or update resources in Docker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker MCP Server environment.

WHY IT NEEDS A POLICY

Why rename_container needs a policy

Renaming a container is a reversible metadata modification operation (Write category). Severity is medium because while the operation itself is safe, renaming a running or important container could cause service disruption if dependent systems rely on the old name, and incorrect renaming could impact container identification and orchestration.

From the tool's definition Tool description states 'Rename a Docker container' which modifies container metadata reversibly. The name/metadata can be changed again without data loss or cascade effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_container Rate-limited

rename_container 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": {
    "rename_container": {
      "limits": [
        {
          "counter": "rename_container_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 Docker MCP Server, so you can run agents against it safely.

FAQ

Questions about rename_container

What does the rename_container tool do? +

Rename a Docker container. It is categorised as a Write tool in the Docker 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 rename_container? +

Register the Docker MCP Server MCP server in PolicyLayer and add a rule for rename_container: 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 Docker MCP Server. Nothing to install.

What risk level is rename_container? +

rename_container is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_container? +

Yes. Add a rate_limit block to the rename_container 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 rename_container completely? +

Set action: deny in the PolicyLayer policy for rename_container. 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 rename_container? +

rename_container is provided by the Docker MCP Server MCP server (swartdraak/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.