Delete a registry from Mittwald.
AI agents call mittwald_registry_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.
The tool performs a delete operation that cannot be undone. Deleting a registry is a destructive action that permanently removes configuration or service data. This is more severe than Write (which is reversible) and represents a high blast radius if invoked incorrectly by an AI agent, as recovery would require manual intervention or backups.
From the tool's definition Tool name 'mittwald_registry_delete' and description 'Delete a registry from Mittwald' explicitly indicate irreversible deletion of data/configuration.
Attacks that exploit this kind of access
Delete a registry from Mittwald. 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_registry_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_registry_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_registry_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_registry_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_registry_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.
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 →