Create a new named volume inside a project stack.
AI agents use mittwald_volume_create to create or update resources in Mittwald MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mittwald MCP Server environment.
This tool creates a new volume (storage resource) within a project, which is a reversible write operation. It modifies the project infrastructure by adding a new storage component, but the action can be undone by deleting the volume. This is not destructive (deletion is permanent), not financial, not read-only, and not arbitrary code execution.
From the tool's definition Tool name 'mittwald_volume_create' and description 'Create a new named volume inside a project stack' explicitly indicate creation of a new resource.
Attacks that exploit this kind of access
Create a new named volume inside a project stack. It is categorised as a Write tool in the Mittwald MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_volume_create: 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_create 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 mittwald_volume_create 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_create. 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_create 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 →