Delete an entity from the knowledge graph. This will also remove all relationships connected to this entity.
AI agents call binelek_delete_entity to permanently remove resources in Binelek MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from the knowledge graph without a reversible operation. Deletion of entities and their relationships cannot be undone through normal tool operations and represents irreversible data loss. The blast radius is high as an AI agent invoking this without proper safeguards could delete critical entities, orphaning data and breaking integrity of the knowledge graph.
From the tool's definition Tool name is 'binelek_delete_entity' and description states 'Delete an entity from the knowledge graph. This will also remove all relationships connected to this entity.' The use of 'delete' and the irreversible removal of both the entity and its…
Attacks that exploit this kind of access
Delete an entity from the knowledge graph. This will also remove all relationships connected to this entity. It is categorised as a Destructive tool in the Binelek MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Binelek MCP Server MCP server in PolicyLayer and add a rule for binelek_delete_entity: 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 Binelek MCP Server. Nothing to install.
binelek_delete_entity 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 binelek_delete_entity 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 binelek_delete_entity. 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.
binelek_delete_entity is provided by the Binelek MCP Server MCP server (k5tuck/binelek-mcp-server). 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 →