list_group_users
AI agents call list_group_users to retrieve information from Okta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates users belonging to a group. The name and context (alongside write/execute/destructive sibling tools) clearly indicate it queries data with no side effects. While it may expose sensitive user information depending on Okta configuration, the operation itself is non-destructive and reversible.
From the tool's definition Tool name 'list_group_users' indicates a retrieval operation that queries group membership data without modifying state. The verb 'list' is a classic Read operation pattern.
Attacks that exploit this kind of access
list_group_users. It is categorised as a Read tool in the Okta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Okta MCP Server MCP server in PolicyLayer and add a rule for list_group_users: 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.
list_group_users 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 list_group_users 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 list_group_users. 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.
list_group_users 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 →