Delete a knowledge node and all its edges, votes, and proofs. Only the creating agent can delete.
AI agents call delete_node to permanently remove resources in Agent-hive — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (knowledge nodes and associated metadata) with no undo capability. While access is restricted to the creating agent ('Only the creating agent can delete'), the operation itself is irreversible and constitutes data destruction.
From the tool's definition Tool description explicitly states: 'Delete a knowledge node and all its edges, votes, and proofs.' The verb 'Delete' combined with 'all its edges, votes, and proofs' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a knowledge node and all its edges, votes, and proofs. Only the creating agent can delete. It is categorised as a Destructive tool in the Agent-hive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agent-hive 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 Agent-hive. 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 Agent-hive MCP server (kelvinyuefanli/agent-hive). 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 →