← All MCP tools

Pause board

pause_board
Write

What it does

Stop the whole board: every agent on this account stops being handed work until a human resumes it. This is pause_task one tier up, and the difference is what it is FOR — pause_task takes one task off the queue and you carry on with the rest; this says the run itself should not continue. Use it when what you hit is not about one task: the account's credentials are gone, every task is failing the same way, you are looping across tasks rather than inside one, or you can see a run about to spend a lot for nothing. Prefer pause_task when the wall is one task's. After this, list_my_tasks and next_task both REFUSE and give back your reason instead of an empty queue — deliberately, so the run that finds the board stopped logs why it stopped rather than "nothing to do". Work you already hold is not stranded: you can still comment on, tick off and close out a task in progress. reason is required and is the whole value of the call. You cannot un-pause: resuming is a human action in the app, so an agent that stopped the board can't restart it. Pass workspace_id when you belong to more than one workspace — list_workspaces has the ids.

Parameters

NameTypeRequiredDescription
workspace_idstringOptional

Which board to stop. Optional when you only belong to one workspace; required otherwise, so a stop this wide is never aimed by guesswork.

reasonstringRequired

What you hit, and what you'd already tried. Shown on the workspace and handed back to every later queue call.

Annotations

The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.

Read-onlyreadOnlyHint: false
Changes data in your Done account.
DestructivedestructiveHint: false
Only adds or reads; nothing already there is removed or overwritten.
IdempotentidempotentHint: false
Each call can add something new, such as a comment, a run or a task.
Open worldopenWorldHint: false
Touches only your own Done account.

Which tokens can call it

A connection made with OAuth has full access. A token from Settings → Agent access → Extra MCP tokens can be narrowed, and a narrowed token never sees beyond its project or workspace.

  • Full accessAllowed
  • Read-only tokenRefused
  • Single-project tokenRefused
  • Single-workspace tokenAllowed

Try it

With Done connected, ask your assistant something like:

“Every deploy is failing. Stop the whole board until I've looked.”

Connect Done to your assistant

One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client:

MCP setup overview →