AI agents call okta_get_user_make_request 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 user information from Okta, a critical identity and access management system. While it is non-destructive and non-modifying (Read category), the severity is medium rather than low because user data in Okta contains sensitive identity information (emails, user IDs, attributes, group memberships, application assignments) that could be exploited by a compromised agent to map organizational structure…
From the tool's definition Tool name contains 'get_user' which retrieves user data; no modification verb (create, delete, update) present. Sibling tools show clear patterns: 'create_', 'delete_', 'deactivate_' for write/destructive actions, while 'list_' and 'get_' retrieve data.
Documented attack patterns abuse exactly the kind of access okta_get_user_make_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Okta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for okta_get_user_make_request:
{
"version": "1",
"default": "deny",
"tools": {
"okta_get_user_make_request": {}
}
}okta_get_user_make_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
okta_get_user_make_request. 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 okta_get_user_make_request: 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.
okta_get_user_make_request 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_make_request 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_make_request. 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_make_request is provided by the Okta MCP Server MCP server (yiyangli/okta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Okta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Okta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.