List persistent volumes that belong to a project stack.
AI agents call mittwald_volume_list to retrieve information from Mittwald MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing persistent volumes in a project stack. It performs no writes, deletions, code execution, or financial transactions. The blast radius of misuse is minimal: an attacker gains visibility into storage infrastructure but cannot modify, delete, or execute operations. Classification as Read is appropriate.
From the tool's definition Tool name contains 'list' and description states 'List persistent volumes' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List persistent volumes that belong to a project stack. It is categorised as a Read tool in the Mittwald MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_volume_list: 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 Mittwald MCP Server. Nothing to install.
mittwald_volume_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mittwald_volume_list 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 mittwald_volume_list. 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.
mittwald_volume_list is provided by the Mittwald MCP Server MCP server (mittwald/mcp-server). 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 →