DESTRUCTIVE — closes the live browser tab(s) AND removes the tree node entirely (compound of ghost_node + delete_node, but bypasses delete_node\
AI agents call delete_live_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 performs irreversible deletion of data structures (tree nodes) and forcibly closes browser tabs. The explicit "DESTRUCTIVE" label in the description, combined with the compound nature removing both the tab and the node record, places this in the Destructive category (most severe among Read/Write/Execute/Destructive). The inability to undo these operations and the destructive intent justify high severity.
From the tool's definition Tool description explicitly states "DESTRUCTIVE — closes the live browser tab(s) AND removes the tree node entirely" and indicates it "bypasses delete_node". The tool irreversibly removes data (tree node) and closes browser tabs, actions that cannot be undone.
Attacks that exploit this kind of access
DESTRUCTIVE — closes the live browser tab(s) AND removes the tree node entirely (compound of ghost_node + delete_node, but bypasses delete_node\. 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_live_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_live_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_live_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_live_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_live_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 →