This record as markdown: /tools/docker/create-volume.md
What create_volume does on Docker
AI agents use create_volume to create or update resources in Docker, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker environment.
Why create_volume is rated Medium
This tool creates persistent storage volumes, a reversible operation. It does not delete, destroy, or execute arbitrary code. While it modifies the Docker environment state, volumes are standard infrastructure resources and creation is non-destructive.
From the tool's definition Tool name and description explicitly state 'Create a Docker volume', which creates a new storage resource within Docker.
Attacks that exploit this kind of access
The rule that runs create_volume safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_volume, this is the rule to start with:
create_volume 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every create_volume call is checked against it from then on.
Questions about create_volume
Create a Docker volume. It is categorised as a Write tool in the Docker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docker MCP server in PolicyLayer and add a rule for create_volume: 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. Nothing to install.
create_volume is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_volume 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 create_volume. 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.
create_volume is provided by the Docker MCP server (@ckreiling/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue