rdm_lookups_list_tool
AI agents call rdm_lookups_list_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 empty description, the naming convention ('list') and context within an MDM platform strongly suggest this tool retrieves or queries lookup reference data. This is a read operation with minimal blast radius. Confidence is moderate due to the lack of descriptive text, but the naming pattern is unambiguous for list operations in typical API conventions.
From the tool's definition Tool name 'rdm_lookups_list_tool' contains 'list', which is a read-only retrieval operation. The suffix '_list_tool' strongly indicates enumeration/querying of lookup data without modification.
Attacks that exploit this kind of access
rdm_lookups_list_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 rdm_lookups_list_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.
rdm_lookups_list_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 rdm_lookups_list_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 rdm_lookups_list_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.
rdm_lookups_list_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 →