get_identities_for_beneficiary
AI agents call get_identities_for_beneficiary to retrieve information from Omada Identity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves identity information associated with a beneficiary through the Omada Identity Governance system. This is a read-only query operation with no side effects—it does not create, modify, delete, or execute external operations.
From the tool's definition Tool name 'get_identities_for_beneficiary' indicates a retrieval operation. The function prefix 'get_' and context within an identity governance system suggests querying identity data.
Attacks that exploit this kind of access
get_identities_for_beneficiary. It is categorised as a Read tool in the Omada Identity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Omada Identity MCP Server MCP server in PolicyLayer and add a rule for get_identities_for_beneficiary: 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 Omada Identity MCP Server. Nothing to install.
get_identities_for_beneficiary 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_identities_for_beneficiary 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_identities_for_beneficiary. 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_identities_for_beneficiary is provided by the Omada Identity MCP Server MCP server (omadaidentity/omada-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 →