search_entities_tool
AI agents call search_entities_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.
Despite the empty description, the tool name clearly indicates a search operation on entities within the master data management platform. Search operations are retrieval-only with no stated side effects. The low severity reflects that searching/querying data has minimal blast radius even if misused, as it cannot modify, delete, or execute external operations.
From the tool's definition Tool name 'search_entities_tool' combined with server context showing 'entity operations' and 'natural language' interaction patterns. The naming convention (search_*_tool) follows read-only operation patterns typical of query/retrieval tools.
Attacks that exploit this kind of access
search_entities_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 search_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.
search_entities_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 search_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 search_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.
search_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 →