create_container_backup · MCP Developer Server MCP

WHAT IT DOES

What create_container_backup does on MCP Developer Server

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

WHY IT NEEDS A POLICY

Why create_container_backup needs a policy

Backup creation modifies system state by writing backup artifacts, but is reversible and non-destructive. It does not delete, execute arbitrary commands, or move money. The medium severity reflects that large backups could consume significant resources, and backups could potentially be used to exfiltrate data, but the operation itself is not inherently harmful if used as intended.

From the tool's definition Tool creates a backup, which is a write operation that generates new data/files. Description states 'Create a backup of a container and its data' — explicitly a creation action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_container_backup Rate-limited

create_container_backup 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_backup": {
      "limits": [
        {
          "counter": "create_container_backup_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 MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about create_container_backup

What does the create_container_backup tool do? +

Create a backup of a container and its data. It is categorised as a Write tool in the MCP Developer 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_backup? +

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

What risk level is create_container_backup? +

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

Can I rate-limit create_container_backup? +

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

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

create_container_backup is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.