get_user_last_location

THE RISK

Low Risk

Why get_user_last_location needs a policy

This tool retrieves historical login and location data from system logs without altering any state. It is a pure read operation. Severity is medium (not low) because location and login metadata can be sensitive information useful for user tracking or surveillance if misused by an agent; however, it lacks the blast radius of Execute, Destructive, or Financial operations.

From the tool's definition Tool description explicitly states 'Retrieve the last known location and login information' with no modification, deletion, or execution capability mentioned.

Documented attack patterns abuse exactly the kind of access get_user_last_location gives an agent:

POLICY

How to control get_user_last_location

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 get_user_last_location:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_last_location": {}
  }
}

get_user_last_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Okta MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Okta MCP Server tools

Destructive delete_group Delete a group from Okta Destructive delete_user Delete a user from Okta (must be deactivated first) Destructive deactivate_user Deactivate a user in Okta Destructive suspend_user Suspend a user in Okta Execute run_onboarding_workflow Run a complete onboarding workflow for multiple users from CSV data Write remove_user_from_group Remove a user from a group in Okta Write provision_applications Provision application access for multiple users Write unsuspend_user Unsuspend a user in Okta

All 21 Okta MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_user_last_location

What does the get_user_last_location tool do? +

Retrieve the last known location and login information for a user from Okta system logs. It is categorised as a Read tool in the Okta MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_last_location? +

Register the Okta MCP Server MCP server in PolicyLayer and add a rule for get_user_last_location: 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.

What risk level is get_user_last_location? +

get_user_last_location is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_last_location? +

Yes. Add a rate_limit block to the get_user_last_location 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.

How do I block get_user_last_location completely? +

Set action: deny in the PolicyLayer policy for get_user_last_location. 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.

What MCP server provides get_user_last_location? +

get_user_last_location is provided by the Okta MCP Server MCP server (kapilduraphe/okta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Okta MCP Server tool call.

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.

CHECK YOUR STACK →