Permanently delete an area by UID. This action cannot be undone.
AI agents call delete_area to permanently remove resources in Tududi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete_area removes data that cannot be recovered. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius depends on what data is contained in the area being deleted, the permanent nature of the operation and lack of recovery mechanism justifies high severity.
From the tool's definition Tool description explicitly states: "Permanently delete an area by UID. This action cannot be undone." The use of "permanently" and "cannot be undone" unambiguously indicates irreversible data deletion.
Attacks that exploit this kind of access
Permanently delete an area by UID. This action cannot be undone. It is categorised as a Destructive tool in the Tududi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tududi MCP Server MCP server in PolicyLayer and add a rule for delete_area: 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 Tududi MCP Server. Nothing to install.
delete_area 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 delete_area 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 delete_area. 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.
delete_area is provided by the Tududi MCP Server MCP server (jeanbispo/tududi-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 →