• TERMINATED
  • AUDITED
  • MANUAL
  • SECURED

How to revoke user sessions with your AI

Connect Dynamic (Web3 Auth) once. From then on, you can tell your agent to kill any active session the moment you spot a security risk.

Ask AI about this page

Short answer

How can I kill user sessions using my AI?

You identify the specific session or user through your agent and then command it to terminate that access. This lets you stop unauthorized activity without digging through a dashboard. You'll see the specific outcomes below.

The results

Security outcomes

What happens after you give the command.

TERMINATED

Active sessions end

The AI invalidates the session token. The user is kicked out of the application immediately.

AUDITED

Access logs updated

Your agent can check which sessions are currently active. You get a clear view of who is logged in before you act.

MANUAL

Human oversight required

The AI won't delete user accounts or change core database permissions. You stay in control of permanent account deletions.

SECURED

Risk is mitigated

By revoking the session, the AI closes the window for an attacker. You stop the breach before it spreads.

The workflow

What your AI does when suspicious activity is flagged.

The AI acts as your security operator, moving from detection to enforcement.

  1. Identify the threat

    Your agent looks through the current list of active users and their session details to find the outlier.

    revoke_session
  2. Confirm the target

    The AI identifies the specific session ID or user identifier that needs to be neutralized.

    revoke_session
  3. Execute revocation

    The agent calls the specific tool to invalidate the session and stop all further requests from that user.

    revoke_session
  4. Verify the kill

    The AI checks the session status again to ensure the connection is truly dead.

    revoke_session

Try it

Copy these to start.

Use these prompts to trigger the revocation process.

Starting points

Replace the bracketed text with your actual user IDs or session details.

Dynamic Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_gXBoI5r4BKVPMeqMtdIlOVxAA8PjWxfSeDZ2Jhgp/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Dynamic capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "dynamic-web3-auth-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_gXBoI5r4BKVPMeqMtdIlOVxAA8PjWxfSeDZ2Jhgp/mcp"
    }
  }
}
Copy into chat04
  • Revoke the session for user_8829 immediately.

  • Find all active sessions for the account 'dev_test_user' and kill them.

  • Check if there are any active sessions from IP addresses outside the US, then revoke them.

  • I see suspicious activity on session_abc123. Revoke it now.

  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Start here

Connect Dynamic (Web3 Auth) once, then ask.

Just link your account once. Your credentials stay encrypted, and you can start managing sessions through your AI client immediately.

Connect Dynamic (Web3 Auth) to your AI

FAQ

How this task behaves

  • 01

    Can the AI delete my entire user database?

    No. The AI only has the ability to revoke specific sessions via the provided tools.

  • 02

    Will the AI automatically revoke sessions without my permission?

    No. The AI only performs the revocation when you explicitly command it to do so in chat.

  • 03

    Does this work for all Web3 wallets?

    Yes, it works for any session managed through the Dynamic (Web3 Auth) provider.

  • 04

    Can the AI change a user's password?

    No. The tool is strictly for session revocation, not for modifying user credentials or passwords.

  • 05

    How fast is the session termination?

    The AI sends the command to the Dynamic (Web3 Auth) API, which invalidates the session immediately.

  • More questions about Dynamic (Web3 Auth)? The Connector page answers them. See everything the Dynamic (Web3 Auth) Connector can do

Connect Dynamic to Claude, Cursor, ChatGPT & more