Call browser.remove_domain
Take ONE site off this workspace's browsing list — the allowed sites your browser may open — so you may no longer open pages on it: 'remove example.com from the browsing list', 'stop letting the browser open that site', 'take our old supplier off the allowed sites'. Use it whenever the operator wants you to stop visiting a site or to withdraw browser access to it; the list is this workspace's own setting, and this verb is how you change it. Call it on every such ask, even when earlier messages or what you remember say the site was already taken off: the list also changes on the Settings screen and by other people, and only this call reads it as it is now. Name the site as it is written on the list, like 'example.com'. Calling it raises the approval card, so call it on the ask; only an account Owner or Admin can approve it, and once approved the site stays off the list until someone adds it again. A site that is not on the list is left as it is, and nothing is charged. Not for adding a site to the list — that is browser.add_domain. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/browser.remove_domain
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 6 revisions of this API.