Create a group in the Okta organization.
AI agents use create_group to create or update resources in Okta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Okta MCP Server environment.
This tool creates new groups in Okta, which modifies the organization's identity infrastructure. While reversible (groups can be deleted via confirm_delete_group), it affects access control and organizational structure. It is not Read (no data retrieval), not Execute (no code/script execution), not Destructive (creation is reversible), not Financial (no money movement). Write is the appropriate category.
From the tool's definition Tool description: 'Create a group in the Okta organization.' The verb 'create' indicates data modification that is reversible (groups can be deleted). This is a write operation that modifies organizational structure.
Attacks that exploit this kind of access
Create a group in the Okta organization. It is categorised as a Write tool in the Okta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Okta MCP Server MCP server in PolicyLayer and add a rule for create_group: 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 Okta MCP Server. Nothing to install.
create_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_group 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 create_group. 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.
create_group is provided by the Okta MCP Server MCP server (pranav-okta/okta-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 →