Surface candidate pairs of entities likely to be duplicates. Read-only — never auto-merges. Combines embedding similarity, shared-neighbor overlap, and name-token Jaccard. Same-type only. Use to triage entity-explosion before running graph_merge (destructive consolidation) or graph_relate with AL...
AI agents call graph_merge_suggestions to retrieve information from Graph-Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it is read-only and never performs any auto-merging. It only surfaces/identifies candidate duplicate entity pairs using similarity metrics, making it a pure query/analysis tool with no side effects. The description also frames it as a precursor to destructive/write operations (graph_merge or graph_relate), but the tool itself performs none of those actions.
From the tool's definition Read-only — never auto-merges. Surface candidate pairs of entities likely to be duplicates.
Attacks that exploit this kind of access
Surface candidate pairs of entities likely to be duplicates. Read-only — never auto-merges. Combines embedding similarity, shared-neighbor overlap, and name-token Jaccard. Same-type only. Use to triage entity-explosion before running graph_merge (destructive consolidation) or graph_relate with ALIAS_OF (soft alias). It is categorised as a Read tool in the Graph-Memory MCP Server, which means it retrieves data without modifying state.
Register the Graph-Memory MCP server in PolicyLayer and add a rule for graph_merge_suggestions: 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 Graph-Memory. Nothing to install.
graph_merge_suggestions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the graph_merge_suggestions 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 graph_merge_suggestions. 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.
graph_merge_suggestions is provided by the Graph-Memory MCP server (stevepridemore/graph-memory). 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 →