This record as markdown: /tools/mittwald-mcp-server/mittwald-stack-delete.md
What mittwald_stack_delete does on Mittwald MCP Server
AI agents call mittwald_stack_delete to permanently remove resources in Mittwald MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mittwald_stack_delete is rated Critical
This tool performs a destructive operation that cannot be undone—deleting an entire stack likely removes associated configurations, deployments, and data. This represents high blast radius if misused by an AI agent (e.g., deleting a production stack).
From the tool's definition Tool name 'mittwald_stack_delete' with description 'Delete a stack.' indicates irreversible deletion of infrastructure/application stack resources.
Attacks that exploit this kind of access
The rule that runs mittwald_stack_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mittwald MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mittwald_stack_delete, this is the rule to start with:
mittwald_stack_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mittwald MCP Server, apply this rule, and every mittwald_stack_delete call is checked against it from then on.
Questions about mittwald_stack_delete
Delete a stack. It is categorised as a Destructive tool in the Mittwald MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mittwald MCP Server MCP server in PolicyLayer and add a rule for mittwald_stack_delete: 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_stack_delete 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 mittwald_stack_delete 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_stack_delete. 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_stack_delete 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.
More on Mittwald MCP Server, and thousands of servers like it.
Across the catalogue