Permanently deletes a note from a library or the main tree. Cloud-side delete is automatic on next persist (the per-scope notes sync diffs current ids against existing Supabase rows and removes missing ones). LAST-NOTE BEHAVIOR: this op allows deleting any note including the only note in a scope....
AI agents call delete_note to permanently remove resources in Pinako AI Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data without the ability to restore it. Permanent deletion of user data from both local and cloud storage qualifies as Destructive, which is more severe than Write or Execute. The high severity reflects that an AI agent with misguided instructions could permanently destroy user notes and library data.
From the tool's definition Tool name is 'delete_note' and description explicitly states 'Permanently deletes a note' and 'this op allows deleting any note'.
Attacks that exploit this kind of access
Permanently deletes a note from a library or the main tree. Cloud-side delete is automatic on next persist (the per-scope notes sync diffs current ids against existing Supabase rows and removes missing ones). LAST-NOTE BEHAVIOR: this op allows deleting any note including the only note in a scope. Pinako auto-reseeds an empty notes array with a default. It is categorised as a Destructive tool in the Pinako AI Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for 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 Pinako AI Bridge. Nothing to install.
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 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 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.
delete_note is provided by the Pinako AI Bridge MCP server (teleomorph/pinako-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 →