delete_label
AI agents call delete_label to permanently remove resources in NotesKeep MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (labels) and cannot be reversed. Even though individual note deletion may have lower impact, removing a label that organizes multiple notes affects the organizational structure across the system. This qualifies as Destructive rather than Write because the action is permanent and affects multiple entities.
From the tool's definition Tool name 'delete_label' indicates permanent removal of a label. The server context shows this is part of a note management system where labels are used to organize notes. Deletion of labels cannot be undone and would affect all notes tagged with that label.
Attacks that exploit this kind of access
delete_label. It is categorised as a Destructive tool in the NotesKeep MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NotesKeep MCP Server MCP server in PolicyLayer and add a rule for delete_label: 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 NotesKeep MCP Server. Nothing to install.
delete_label 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_label 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_label. 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_label is provided by the NotesKeep MCP Server MCP server (mariomosca/noteskeep-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 →