merge_entities_tool
AI agents call merge_entities_tool to permanently remove resources in Reltio MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
In MDM platforms like Reltio, merging entities consolidates multiple records into one, which is generally irreversible (or very difficult to undo). The source entities lose their independent existence. This qualifies as Destructive given the irreversible nature of the operation.
From the tool's definition Tool name 'merge_entities_tool' — merging entities in a master data management platform typically combines records irreversibly, destroying the separate identity of the source entities.
Attacks that exploit this kind of access
merge_entities_tool. It is categorised as a Destructive tool in the Reltio MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reltio MCP Server MCP server in PolicyLayer and add a rule for merge_entities_tool: 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 Reltio MCP Server. Nothing to install.
merge_entities_tool 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 merge_entities_tool 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_tool. 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_tool is provided by the Reltio MCP Server MCP server (reltio-ai/reltio-mcp-server). 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 →