Delete a node and its vector from Qdrant.
AI agents call graph_delete_node to permanently remove resources in MCP Roo Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a node and its associated vector from the Qdrant database. Deletion is irreversible and cannot be undone through normal operations. While the blast radius is scoped to a single node (not an entire system), the permanent loss of structured knowledge managed by this persistent memory system qualifies as destructive.
From the tool's definition Tool name is 'graph_delete_node' and description explicitly states 'Delete a node and its vector from Qdrant.' The use of 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a node and its vector from Qdrant. It is categorised as a Destructive tool in the MCP Roo Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Roo Memory MCP server in PolicyLayer and add a rule for graph_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 MCP Roo Memory. Nothing to install.
graph_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 graph_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 graph_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.
graph_delete_node is provided by the MCP Roo Memory MCP server (mcasdfgf/mcp-roo-memory). 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 →