add_user_to_group
AI agents use add_user_to_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 modifies group membership by adding a user to a group, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger external systems unpredictably (Execute). The severity is high because misconfigured group memberships can grant unintended access to resources and affect organizational security posture.
From the tool's definition Tool name 'add_user_to_group' indicates modification of group membership. Sibling tools include 'create_user', 'create_group', and other provisioning/management operations, confirming this server handles identity and access management.
Attacks that exploit this kind of access
add_user_to_group. 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 add_user_to_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.
add_user_to_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 add_user_to_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 add_user_to_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.
add_user_to_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 →