check_graph
v12.5.0 \u2014 Detect orphan relations (from/to references a missing entity), missing parents (entity.parentId references a missing entity), and hierarchy cycles. Reports findings. With apply=true, deletes orphan relations and clears missing parentIds; cycles are always reported but never auto-re...
This record as markdown: /tools/danielsimonjr-memory-mcp/check-graph.md
What check_graph does on Enhanced Knowledge Graph Memory Server
AI agents call check_graph to permanently remove resources in Enhanced Knowledge Graph Memory Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why check_graph is rated Critical
When invoked with apply=true, this tool irreversibly deletes orphan relations and clears parentId references in the knowledge graph. Deletion of graph edges and clearing of structural references cannot be undone, placing this firmly in the Destructive category. The default read/report mode is non-destructive, but the tool's capability to permanently remove data makes it Destructive by the most-severe-applicable rule.
From the tool's definition With apply=true, deletes orphan relations and clears missing parentIds
Attacks that exploit this kind of access
The rule that runs check_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_graph, this is the rule to start with:
check_graph 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 Enhanced Knowledge Graph Memory Server, apply this rule, and every check_graph call is checked against it from then on.
Questions about check_graph
v12.5.0 \u2014 Detect orphan relations (from/to references a missing entity), missing parents (entity.parentId references a missing entity), and hierarchy cycles. Reports findings. With apply=true, deletes orphan relations and clears missing parentIds; cycles are always reported but never auto-repaired (no safe default for which edge to break). It is categorised as a Destructive tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for check_graph: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
check_graph 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 check_graph 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 check_graph. 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.
check_graph is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
This server
Across the catalogue