create_access_request · Omada Identity MCP Server MCP

WHAT IT DOES

What create_access_request does on Omada Identity MCP Server

AI agents use create_access_request to create or update resources in Omada Identity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omada Identity MCP Server environment.

WHY IT NEEDS A POLICY

Why create_access_request needs a policy

The tool creates new access requests in an identity governance system, which is a reversible write operation. Severity is high because misconfigured access requests could grant unintended permissions, affecting system security posture. However, it is not Destructive (requests can be revoked/canceled) or Financial (no money movement). The empty description limits confidence to 0.85 rather than higher.

From the tool's definition Tool name 'create_access_request' and server context (Omada Identity Governance system for access requests) indicate the tool creates or modifies identity access data. Description is empty, reducing confidence slightly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_access_request Rate-limited

create_access_request stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_access_request": {
      "limits": [
        {
          "counter": "create_access_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Omada Identity MCP Server, so you can run agents against it safely.

FAQ

Questions about create_access_request

What does the create_access_request tool do? +

create_access_request. It is categorised as a Write tool in the Omada Identity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_access_request? +

Register the Omada Identity MCP Server MCP server in PolicyLayer and add a rule for create_access_request: 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.

What risk level is create_access_request? +

create_access_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_access_request? +

Yes. Add a rate_limit block to the create_access_request 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.

How do I block create_access_request completely? +

Set action: deny in the PolicyLayer policy for create_access_request. 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.

What MCP server provides create_access_request? +

create_access_request 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.