delete_entity_edge
Delete an entity edge from the graph memory.
This record as markdown: /tools/aegntic-aegntic-mcp/delete-entity-edge.md
What delete_entity_edge does on Obsidian Elite RAG MCP Server
AI agents call delete_entity_edge to permanently remove resources in Obsidian Elite RAG MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_entity_edge is rated Critical
The tool performs irreversible deletion of graph structure data (entity edges representing relationships in the RAG knowledge graph). While individual edge deletion may not destroy entire documents, it permanently removes semantic relationships that cannot be recovered without manual intervention. This qualifies as Destructive rather than Write because deletion is not reversible through normal operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete an entity edge from the graph memory' - this irreversibly removes a relationship/edge from the knowledge graph that maps semantic connections in the vault.
Attacks that exploit this kind of access
The rule that runs delete_entity_edge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_entity_edge, this is the rule to start with:
delete_entity_edge is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every delete_entity_edge call is checked against it from then on.
Questions about delete_entity_edge
Delete an entity edge from the graph memory. It is categorised as a Destructive tool in the Obsidian Elite RAG MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for delete_entity_edge: 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 Obsidian Elite RAG MCP Server. Nothing to install.
delete_entity_edge 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_entity_edge 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_entity_edge. 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_entity_edge is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
Across the catalogue