Skip to main content
Glama

Writ Cloud

Ask the user to step in

writ_browser_ask_user

Asks the Writ user (the person who owns this Writ account) to step in on an open browser session: complete a security check (CAPTCHA, 'confirm it's you', Arkose/hCaptcha/reCAPTCHA puzzle) in the live browser, supply a one-time 2FA code, or answer a question only they can decide. For: writ_browser_act returning security_check with auto_solved false; a twofa action failing with twofa_mint_failed or twofa_no_persona (kind='twofa'); any point where only a human can proceed. A one-time code is NOT a first-resort ask: twofa_method_mismatch and twofa_verify_method mean the page is on a method other than the persona's, which the page itself switches or resends, as the message says. With kind='twofa' the user pastes the code in the Writ app and Writ enters it server-side, so it never reaches you; kind='question' returns the user's text, so a code sent that way would reach the conversation. The session pauses (the user is notified in the app and by email and controls the live page); this call holds up to 60s and returns status 'answered' (with solved / answer, or entered for twofa), 'waiting_for_user' (the same call with the same session_id keeps waiting while the user holds the page), or 'expired'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNocaptcha: the user completes a check in the live browser. question: the user answers in text. twofa: the user supplies the one-time code the page is asking for; Writ types it server-side and returns `entered`, never the code.
questionNoThe question, in one short sentence (required for kind 'question').
session_idYes
wait_secondsNoHold up to this long (1-60, default 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.