Delete a project
AI agents call karea_delete_project to permanently remove resources in Karea — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a project is an irreversible operation that destroys data and cannot be undone. This satisfies the Destructive category definition. Severity is high because a project likely contains multiple tasks, subtasks, notes, and associated data; its deletion would have significant blast radius if triggered by an AI agent in error. Confidence is high given the explicit 'Delete' verb and unambiguous semantics.
From the tool's definition Tool name 'karea_delete_project' and description 'Delete a project' explicitly indicate permanent removal of a project resource.
Attacks that exploit this kind of access
Delete a project. It is categorised as a Destructive tool in the Karea MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Karea MCP server in PolicyLayer and add a rule for karea_delete_project: 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 Karea. Nothing to install.
karea_delete_project 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 karea_delete_project 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 karea_delete_project. 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.
karea_delete_project is provided by the Karea MCP server (starecz/karea-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 →