/mcp
path, exposing one tool: a search across every page here. Add it to your coding tool and the
assistant answers from the current pages rather than from whatever it remembers.
The configuration
For Cursor, inmcp.json:
servers block:
/mcp on whatever host serves this site.
Three questions it can now answer
- What happens in CTRLRun when a tool call times out? The assistant finds
Outcomes and AMBIGUOUS and answers that a timeout is
AMBIGUOUS, notFAILED, and that a retry is refused until a human or a reconcile hook resolves it. - How do I put an approval in front of one MCP tool but not another? It finds the
policy reference and the
gateway page: one entry per tool,
approveon one,allowon the other. - Does the receipt chain prove who wrote a receipt? It finds Receipts and evidence and answers no: the chain detects alteration and is not a signature.
What it is not
It is not enforcement. An assistant that can search this documentation can tell you what the gateway does; it cannot stand in the agent’s path. An agent that called a CTRLRun tool to check its own actions could also choose not to, which is why the gateway is a process between the agent and its tools and not a tool the agent picks.Screenshot
One image, when the site is live: the editor’s MCP settings panel withctrlrun-docs listed
and its one tool, search, beside a chat pane where the first question above was asked and
answered with the link to the AMBIGUOUS page visible. 1600×1000, the editor’s default theme, no
other servers in the list.