get_resources_for_beneficiary
AI agents call get_resources_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.
This tool queries resource information associated with a beneficiary within Omada Identity Governance, which is a read operation with no side effects. Severity is medium rather than low because it accesses identity and resource data that could be sensitive if exposed to an unauthorized agent, though the operation itself is non-destructive.
From the tool's definition Tool name 'get_resources_for_beneficiary' indicates data retrieval. The description is empty, but the naming pattern aligns with other sibling tools like 'get_access_requests', 'get_all_omada_identities', and 'get_approval_details', which are read operations.
Attacks that exploit this kind of access
get_resources_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_resources_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_resources_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_resources_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_resources_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_resources_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 →