check_access_request_policy
AI agents call check_access_request_policy 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.
'check' typically indicates a read/query operation (checking policy configuration or status). Without description, this appears to be a policy lookup or validation read operation. Severity is medium because identity governance policies are sensitive but reading them lacks destructive or execute side effects.
From the tool's definition Tool name 'check_access_request_policy' contains 'check' (retrieval verb). No description provided to verify behavior. Sibling tools include 'get_' and 'create_' verbs suggesting this server performs read/write operations on identity governance.
Attacks that exploit this kind of access
check_access_request_policy. 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 check_access_request_policy: 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.
check_access_request_policy 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 check_access_request_policy 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 check_access_request_policy. 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.
check_access_request_policy 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.
check_access_request_policy 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 →