query_omada_entity
AI agents call query_omada_entity 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 appears to retrieve or query identity and resource data from Omada Identity Governance without modifying data. Query operations on identity systems carry medium severity because sensitive PII and access control information could be exposed if an agent misuses the tool to extract unintended data, but the primary risk is information disclosure rather than destructive action.
From the tool's definition Tool name 'query_omada_entity' and server context indicate data retrieval; server description mentions 'identity, resource, and access request queries through OData and GraphQL APIs'.
Attacks that exploit this kind of access
query_omada_entity. 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_entity: 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_entity 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_entity 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_entity. 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_entity 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 →