Works with the AI Agents you already use
ast okta
Investigate Okta identity incidents, audit MFA coverage, and respond to threats with session revocation.
$49
ast okta
Example session with this skill installed
Search the Okta System Log for any successful logins from IP 192.0.2.15 in the last 24 hours. Show me the user and the timestamp.
- Read your context and instructions
- Compiled the ast okta
I have searched the Okta System Log for successful login events originating from 192.0.2.15 within the requested 24-hour window.
Okta System Log Results
| Timestamp (UTC) | Actor | Event Type | Outcome |
|---|---|---|---|
| 2023-10-27T09:14:22Z | j.doe@example.com | user.session.start | SUCCESS |
| 2023-10-27T10:05:10Z | a.smith@example.com | user.session.start | SUCCESS |
| 2023-10-27T14:45:30Z | j.doe@example.com | user.session.start | SUCCESS |
Command executed: okta-search logs --filter "client.ipAddress eq \"192.0.2.15\" and outcome.result eq \"SUCCESS\"" --since 24h --json
Gaps
- The search was limited to the
user.session.startevent type for clarity. - No
errorswere reported by the Okta API during this request. - The time window searched was 2023-10-26T16:00:00Z to 2023-10-27T16:00:00Z.
Next steps
- Review the MFA factors for
j.doe@example.comto ensure no unauthorized devices were added.
Needs your approval: Suspend the account for j.doe@example.com if this IP is confirmed malicious. This can be undone via the Okta Admin Console.
- Needs your approval: Revoke all active sessions for both users to force re-authentication.
Connects securely to your tools. The creator never sees your data.
About this skill
Identity incidents in Okta demand fast investigation and precise containment. Manual searching through the Okta System Log or checking MFA coverage across thousands of users slows down your response time. This skill provides a command-line and MCP-based toolkit to audit configurations, hunt through logs, and execute targeted containment actions like session revocation.
What it does
- Identity Investigation performs user lookups, group membership checks, and factor enrollment audits.
- System Log Hunting executes deep searches against Okta System Logs for specific IPs, actors, or events.
- Security Auditing reviews org configurations including policies, zones, app integrations, and IdPs.
- MFA Census identifies users with weak or missing multi-factor authentication coverage.
- Threat Containment suspends compromised accounts and revokes active web sessions or OAuth tokens.
How it works
- Environment Setup run the
install.shscript to build the Python virtual environment and local AST packages. - Credential Management use
sectools secretsto securely map Okta API tokens to the system keychain or a local.envfile. - Diagnostic Check run
sectools doctor --liveto verify connectivity and permission scopes for the Okta domain. - Active Investigation call
okta-searchvia CLI or MCP to retrieve JSON-formatted telemetry and configuration data. - Authorized Response propose a
suspendorrevokeaction, then execute only after receiving explicit user approval.
Frameworks & tools
Built for Python 3.12+, this skill utilizes the AST okta-search CLI and sectools-mcp server. It interfaces directly with Okta org domains via HTTPS.
Why this beats prompting it yourself
Generic LLMs lack direct access to your live Okta environment and often hallucinate API capabilities. This skill provides a structured safety model that requires explicit approval for writes, handles credential storage outside of the chat history, and ensures zero-row results are not misinterpreted as proof of absence.
Use cases
- Identify all users who signed in from a specific malicious IP address today.
- Audit which administrators have not enrolled in phishing-resistant MFA factors.
- Revoke all active sessions and OAuth tokens for a specific user after a laptop theft.
- Compare Classic vs Identity Engine configurations across multiple Okta zones.
Known limitations
Does not support Microsoft Entra ID, Azure AD, on-prem Active Directory, or Auth0. Write actions are strictly limited to account suspension and session revocation; it cannot reset passwords.
No support for Entra ID, Azure AD, or Auth0. Writes limited to suspend and revoke. Requires Python 3.12+. MCP writes require manual gate activation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
File Scopes
Terminal/Shell runs `install.sh`, `okta-search` and `sectools`; Read/Write Files cover the venv, your `~/.config/ast/.env` and optional exports; Environment Variables carry `OKTA_DOMAIN`, `OKTA_API_TOKEN` and the gate; Network Access reaches PyPI at install and your Okta org domain over HTTPS at run time. Reads (users, logs, factors, groups, mfa-coverage, configuration audits) run without prompting. The only writes are `suspend` and `revoke`: the CLI asks [y/N] before each, and over MCP `okta_suspend` / `okta_revoke` are registered only when `SECTOOLS_OKTA_EDIT=1` and the server is restarted; the skill requires your explicit approval of each exact change. Credentials are typed by you into `.env` or the keychain, never into the chat.