Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Sign Out Browser Sessions

revoke_browser_sessions
DestructiveIdempotent

Sign out all browser sessions on a pod’s public ports or across a workspace when a shared computer or leaked session may expose access; preview first, then confirm.

Instructions

Sign out every browser session on a pod's locked ports, only when the user asks: workspace members who opened them in a browser (they stay signed in there for 7 days) have to enter again through the console. Use it when a port was opened on a shared computer, or a session may have leaked. With pod it covers every public port of that pod, and no other pod. all_pods=true (and no pod) covers every pod of the workspace instead: use it only when the user asks for the whole workspace, and pass workspace. It signs out every member at once, the user included: one person's or one computer's session can't be signed out alone, so say that before the user agrees. Browser cookies only: access keys keep working, and connections that are already open (a WebSocket, for example) stay open. It takes a few seconds to apply and can't be undone; calling it again is safe. With confirm=false (default) it only returns a summary and changes nothing; call again with confirm=true and the summary's pod_name (for a whole workspace: all_pods=true and the summary's workspace id) after the user agreed. Only a workspace admin or billing member can do it. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revoke_browser_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
podNoThe pod_name from the pods tool (its display name also works, except with confirm=true: use the `pod_name` the preview returned). Leave it out only together with all_pods=true.
confirmNo
all_podsNo
workspaceNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: 7-day re-sign-in window, cookies vs access keys, live connections (WebSocket) surviving, few-seconds propagation, irreversibility, re-call safety, admin/billing permission requirement, and the confirm=true preview-to-commit flow. Only minor gap is how the summary/preview content looks, though an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the user-consent gate, and the paragraph structure (scope → behavior → confirm flow → operation_id) is easy to follow. It is long and repeats the confirmation gating twice ('call again with confirm=true... after the user agreed' and the operation_id paragraph), costing some tightness for a tool that is nonetheless genuinely destructive and complex.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, workspace-wide, two-phase operation with a preview/commit cycle, the description covers consent, scope selection, permissions, irreversibility, retry/timeout handling via operation_status, and idempotency. An output schema exists, so return-value detail is correctly left out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description has to carry the load and mostly does: it explains pod vs all_pods mutual exclusion, that `workspace` is required with all_pods, that confirm=false is a no-op preview, and the operation_id reuse/UUID rule. It stops short of stating the exact format of a pod_name or workspace id, but the semantics of each parameter are clear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus scope: 'Sign out every browser session on a pod's locked ports.' It also draws the boundary against the sibling credential tool ('Browser cookies only: access keys keep working'), so an agent can distinguish it from revoke_access_key without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use conditions ('when a port was opened on a shared computer, or a session may have leaked'), explicit escalation rule for all_pods=true ('only when the user asks for the whole workspace, and pass `workspace`'), and an explicit precondition ('only when the user asks'). It also names the alternative path (revoke_access_key) by contrast.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.