get_tenant_metadata_tool
AI agents call get_tenant_metadata_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.
The tool name pattern 'get_*' combined with context as a metadata retrieval function from a master data management platform indicates this retrieves tenant configuration or structural information without modifying data. No side effects or destructive capabilities are suggested. Risk is low as metadata queries have minimal blast radius.
From the tool's definition Tool name 'get_tenant_metadata_tool' indicates retrieval of metadata. The 'get_' prefix and lack of mutation language (create, delete, update) suggest a read-only query operation. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
get_tenant_metadata_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_tenant_metadata_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_tenant_metadata_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_tenant_metadata_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_tenant_metadata_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_tenant_metadata_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 →