get_merge_activities_tool
AI agents call get_merge_activities_tool to retrieve information from Reltio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve historical data about merge activities in the MDM system. Even though the description is missing, the naming pattern 'get_*' combined with the term 'activities' (typically logged events) points to a read-only operation that queries existing records without side effects.
From the tool's definition Tool name 'get_merge_activities_tool' suggests retrieval of merge activity records. The description is empty, limiting direct evidence, but the 'get_' prefix and context within a master data management platform indicates a query/retrieval operation rather…
Attacks that exploit this kind of access
get_merge_activities_tool. It is categorised as a Read tool in the Reltio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Reltio MCP Server MCP server in PolicyLayer and add a rule for get_merge_activities_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.
get_merge_activities_tool 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 get_merge_activities_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 get_merge_activities_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.
get_merge_activities_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 →