Delete a note from a task
AI agents call karea_delete_note 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 note is a destructive action that permanently removes data and cannot be undone. This falls under the Destructive category rather than Write (which is reversible). The blast radius is high because an AI agent could accidentally delete important task notes, losing context or documentation. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name contains 'delete' and description states 'Delete a note from a task' — irreversible removal of data.
Attacks that exploit this kind of access
Delete a note 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_note: 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_note 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_note 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_note. 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_note 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 →