query_omada_identity
AI agents call query_omada_identity 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 is a query operation that retrieves identity data from Omada Identity Governance. While the description is empty, the name and context of sibling tools (all 'get_*' operations) strongly indicate this performs read-only queries. The severity is medium rather than low because identity and access data is sensitive in governance systems—misuse could expose or enumerate organizational identities and permissions.
From the tool's definition Tool name 'query_omada_identity' and sibling tools on the server performing queries and retrievals (get_access_requests, get_all_omada_identities, get_approval_details, get_calculated_assignments_detailed,…
Attacks that exploit this kind of access
query_omada_identity. 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 query_omada_identity: 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.
query_omada_identity 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 query_omada_identity 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 query_omada_identity. 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.
query_omada_identity 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 →