check_graph

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/danielsimonjr-memory-mcp/check-graph.md

WHAT IT DOES

What check_graph does on Enhanced Knowledge Graph Memory Server

AI agents call check_graph to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_graph is rated Low

Even though check_graph only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

check_graph is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_graph": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about check_graph

What does the check_graph tool do? +

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 Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_graph? +

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.

What risk level is check_graph? +

check_graph is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_graph? +

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.

How do I block check_graph completely? +

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.

What MCP server provides check_graph? +

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.

KEEP EXPLORING

More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.

This server

All 225 Enhanced Knowledge Graph Memory Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →