Account Custodian Security & access · synthetic account
92-second demo Source

Synthetic — the contract is real, the keys are not.

Interface Passport · Account Custodian

Clean stale account access. Keep approval off the tool surface.

The agent does the tedious work: inspect ten access paths and prepare one exact cleanup. The page keeps the consequential decisions: approval and undo are not tools.

10stale items reviewed
7WebMCP tools exposed
0approval or undo tools
6live origins in the full system
Why this cannot be a generic “are you sure?” dialog

WebMCP enforces least authority at the tool boundary, and apply cannot forge approval through its arguments. A truly human-only boundary still requires browser or host enforcement outside agent-controllable page interactions. The preview is bound to its ID, session, expiry, before-state hash, proposed-state hash, and protected locks. Reversal is page-owned because restoring access is more dangerous than removing it.

Synthetic account

10-item inventory

All active
    Delete account · erase location history Not in the capability vocabulary. The contract cannot take either back, so neither is offered to agents at all.

    On this page, the WebMCP capability surface is the reversibility surface — its registered tools offer nothing the contract cannot take back.

    The complete working project · six distinct WebMCP origins

    One consent contract, tested against six different jobs.

    The tools belong to the page you are viewing and disappear when you leave it. Each destination publishes only the capabilities it can honor.