get_all_omada_identities
AI agents call get_all_omada_identities 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 retrieves identity information from an Omada Identity system without modifying data. It is a Read operation. Severity is high (not critical) because bulk identity data exposure could facilitate social engineering, impersonation, or privilege escalation attacks, but the tool itself does not modify or delete data.
From the tool's definition Tool name 'get_all_omada_identities' indicates retrieval of identity data. Sibling tools like 'get_access_requests', 'get_approval_details', and 'get_calculated_assignments_*' confirm this server performs read operations.
Attacks that exploit this kind of access
get_all_omada_identities. 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_all_omada_identities: 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_all_omada_identities 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_all_omada_identities 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_all_omada_identities. 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_all_omada_identities is provided by the Omada Identity MCP Server MCP server (walkerpauldavid/omadaidentitymcpserver). 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 →