get_user_profile_attributes
AI agents call get_user_profile_attributes 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.
The 'get_' prefix strongly suggests a query/retrieval operation that fetches existing user attributes without side effects. While the description is empty (lowering confidence slightly), the tool name unambiguously indicates a read operation. User profile attribute retrieval is a standard data access operation with no destructive, financial, or executable consequences.
From the tool's definition Tool name 'get_user_profile_attributes' indicates retrieval of user profile data with no modification; naming convention follows standard read operation patterns (get_*); sibling tools show destructive (delete), write (create, add), and execute (activate)…
Attacks that exploit this kind of access
get_user_profile_attributes. 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 get_user_profile_attributes: 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.
get_user_profile_attributes 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 get_user_profile_attributes 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 get_user_profile_attributes. 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.
get_user_profile_attributes 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 →