Retrieve a specific Okta user by ID or login.
AI agents call okta_get_user to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from Okta without modifying or deleting data. It is categorized as Read. However, severity is high because Okta user data often contains sensitive identity and authentication information (email, phone, user status, group memberships, etc.), and an AI agent with this capability could expose personally identifiable information (PII) or facilitate unauthorized access control changes…
From the tool's definition Tool name is 'okta_get_user' and description states 'Retrieve a specific Okta user by ID or login.' The verb 'retrieve' and the action of fetching user data indicates a read-only operation with no data modification.
Attacks that exploit this kind of access
Retrieve a specific Okta user by ID or login. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for okta_get_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.
okta_get_user 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 okta_get_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.
Set action: deny in the PolicyLayer policy for okta_get_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.
okta_get_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.
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 →