get_identity_contexts
AI agents call get_identity_contexts 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 'get_' prefix and context of identity governance queries indicate this retrieves identity context data without modifying it. No side effects are implied by the name or server purpose. Medium severity due to potential sensitivity of identity data exposure; blast radius depends on whether contexts include access levels or permissions that could inform privilege escalation.
From the tool's definition Tool name 'get_identity_contexts' follows Read pattern (get_*); sibling tools include 'get_access_requests', 'get_all_omada_identities', 'get_approval_details' which are clearly retrieval operations. Empty description limits confidence.
Attacks that exploit this kind of access
get_identity_contexts. 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_identity_contexts: 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_identity_contexts 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_identity_contexts 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_identity_contexts. 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_identity_contexts 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.
get_identity_contexts is one line of Omada Identity MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →