Skip to main content
This documentation is an MCP server, hosted with the site by Mintlify at the site’s /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, in mcp.json:
For VS Code and other clients that take a servers block:
Both shapes are the ones Mintlify’s documentation gives for a hosted docs server (read 2026-09-06). The path is always /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, not FAILED, 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, approve on one, allow on 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.

​
Next

Related topics

CTRLRun and MCPUse the LangGraph adapterAn IAM agent that can grant read but never adminApprove from your assistantCTRLRun and agent oversight toolkits