merge_entities
Merge multiple entities into one
This record as markdown: /tools/danielsimonjr-memory-mcp/merge-entities.md
What merge_entities does on Enhanced Knowledge Graph Memory Server
AI agents use merge_entities to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why merge_entities is rated Medium
Merging entities constitutes creating or modifying data in a reversible manner. While it combines multiple records into one (destructive in appearance), the operation itself is typically reversible through undo or version history in a knowledge graph system, and does not permanently delete the underlying data.
From the tool's definition Tool description states 'Merge multiple entities into one' which modifies existing data by combining entities. This is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs merge_entities 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 merge_entities, this is the rule to start with:
merge_entities stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every merge_entities call is checked against it from then on.
Questions about merge_entities
Merge multiple entities into one. It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for merge_entities: 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.
merge_entities is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_entities 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 merge_entities. 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.
merge_entities 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.
Across the catalogue