okta_create_user · Integrations MCP: Risk & Policy

WHAT IT DOES

What okta_create_user does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why okta_create_user needs a policy

Creating users in Okta is a reversible write operation that adds records to an identity management system. While this grants access and creates accounts, it does not irreversibly delete data (Destructive), execute arbitrary code (Execute), nor transfer money (Financial).

From the tool's definition Tool name 'okta_create_user' indicates creation of a new user identity in Okta identity management system. The 'create' verb signals a write operation that modifies the state of the system by adding a new user record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

okta_create_user Rate-limited

okta_create_user 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": {
    "okta_create_user": {
      "limits": [
        {
          "counter": "okta_create_user_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about okta_create_user

What does the okta_create_user tool do? +

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

How do I enforce a policy on okta_create_user? +

Register the Integrations MCP server in PolicyLayer and add a rule for okta_create_user: 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 Integrations MCP. Nothing to install.

What risk level is okta_create_user? +

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

Can I rate-limit okta_create_user? +

Yes. Add a rate_limit block to the okta_create_user 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 okta_create_user completely? +

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

okta_create_user is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.