Manage Docker volumes: list, create, inspect, remove, prune unused.
AI agents call docker_volumes to permanently remove resources in RedisNexus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the tool also includes read operations (list, inspect) and a write operation (create), the presence of 'remove' and 'prune' makes this a Destructive tool. Removing or pruning Docker volumes permanently deletes data and cannot be undone. This poses a high blast radius in a production environment where an AI agent could accidentally destroy persistent data or application state stored in volumes.
From the tool's definition Tool description includes 'remove' and 'prune unused' operations on Docker volumes, which irreversibly delete data that cannot be recovered.
Attacks that exploit this kind of access
Manage Docker volumes: list, create, inspect, remove, prune unused. It is categorised as a Destructive tool in the RedisNexus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RedisNexus MCP server in PolicyLayer and add a rule for docker_volumes: 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 RedisNexus. Nothing to install.
docker_volumes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the docker_volumes 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 docker_volumes. 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.
docker_volumes is provided by the RedisNexus MCP server (rajkumar-madhu/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 →