Delete a closing requisite from a task
AI agents call karea_delete_requisite 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.
The tool performs a destructive action by deleting a requisite, which cannot be undone. This is a core Destructive operation as defined by the classification framework. While the scope is limited to a task's requisite (not the entire task), the action itself is irreversible and could break task management workflows or lose important dependency information.
From the tool's definition Tool name contains 'delete' and description states 'Delete a closing requisite from a task' — this is an irreversible removal operation.
Attacks that exploit this kind of access
Delete a closing requisite from a task. 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_requisite: 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_requisite 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_requisite 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_requisite. 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_requisite 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 →