DESTRUCTIVE — permanently removes a GHOST node (chromeId=null) and its metadata (tags, memos, star color, custom title). For scope=
AI agents call delete_node 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 (node and associated metadata) with no undo mechanism, making it Destructive rather than merely Write. The severity is high because deletion of user's library/bookmark metadata could cause significant data loss, though blast radius is limited to local Pinako extension state rather than external systems.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE — permanently removes a GHOST node' and 'its metadata (tags, memos, star color, custom title)'. The word 'permanently' combined with 'removes' indicates irreversible deletion.
Attacks that exploit this kind of access
DESTRUCTIVE — permanently removes a GHOST node (chromeId=null) and its metadata (tags, memos, star color, custom title). For scope=. 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_node: 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_node 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_node 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_node. 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_node 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 →