How to Add Guardrails and Human Approval to Grok Bot
Contro1 unifies policy, approval and audit for governed Actions across Grok and other agents, and securely manages organizational skills.
Start here
Connect Grok Bot to Contro1: add one MCP address, approve the sign-in, and it acts as you, with every call checked and recorded.
Updated Oct 21, 2026
Grok Bot can install an MCP server by URL when you ask a Bot to. It acts as you: it can use the Actions you hold and nothing more, and every call is recorded as yours.
Grok Bot is a personal agent that xAI runs for you on its own servers, so there is nothing to install. For: Grok Bot. Acts as: You, the person who approves the sign-in. Credential: An OAuth token Grok Bot holds. Contro1 never sees your xAI password..
Grok Bot can install an MCP server by URL when you ask a Bot to. It acts as you: it can use the Actions you hold and nothing more, and every call is recorded as yours.
You need a Contro1 account and a Grok Bot account.
| Step | What to do | What you should see |
|---|---|---|
| Copy the Contro1 MCP address | https://api.contro1.com/api/centcom/mcp | The address https://api.contro1.com/api/centcom/mcp is on your clipboard. |
The same address for every organization. The sign-in, not the address, decides who it acts as.
What you should see: The address https://api.contro1.com/api/centcom/mcp is on your clipboard.
Grok Bot can install an MCP server by URL when you ask a Bot to.
| Step | What to do | What you should see |
|---|---|---|
| Add Contro1 in Grok Bot | https://api.contro1.com/api/centcom/mcp | The Bot adds the server and the Contro1 sign-in page opens. Afterwards Contro1 is listed under Connect apps. |
In a chat with one of your Bots, ask it to add the MCP server at https://api.contro1.com/api/centcom/mcp.
What you should see: The Bot adds the server and the Contro1 sign-in page opens. Afterwards Contro1 is listed under Connect apps.
These start on the Contro1 sign-in page Grok Bot opened.
| Step | What to do | What you should see |
|---|---|---|
| Approve the Contro1 sign-in | On the Contro1 consent page, sign in with your Contro1 account. Leave "Run Actions as you" checked so the app can run Actions; uncheck it if the connection should only read and preview. Then press Authorize. | The Contro1 page closes and you are back in the app, with Contro1 connected. |
| Ask it who you are | In a chat, ask the app: "Who am I in Contro1?" | The app calls the whoami tool, which names you and your organization. If it names somebody else, disconnect Contro1 in the app and connect again with the intended account. |
| Find it on Agents | Open Agents in Contro1. | It is listed as "Cursor (signed in as <you>)". It can use the Actions you hold and nothing more, and every call is recorded as yours. |
| Give it something to do | Connecting grants nothing by itself. Apps allows an application's tools for the organization, and Access gives them to people and agents. Once you hold an Action, ask the app to list its Actions: it calls list_actions, and invoke_action when it needs an application. | list_actions shows the Actions you hold. When the app runs one, Contro1 allows it, refuses it, or waits for a person first, as your organization's policy says. |
On the Contro1 consent page, sign in with your Contro1 account. Leave "Run Actions as you" checked so the app can run Actions; uncheck it if the connection should only read and preview. Then press Authorize.
What you should see: The Contro1 page closes and you are back in the app, with Contro1 connected.
In a chat, ask the app: "Who am I in Contro1?"
What you should see: The app calls the whoami tool, which names you and your organization. If it names somebody else, disconnect Contro1 in the app and connect again with the intended account.
Open Agents in Contro1.
What you should see: It is listed as "Cursor (signed in as <you>)". It can use the Actions you hold and nothing more, and every call is recorded as yours.
Connecting grants nothing by itself. Apps allows an application's tools for the organization, and Access gives them to people and agents. Once you hold an Action, ask the app to list its Actions: it calls list_actions, and invoke_action when it needs an application.
What you should see: list_actions shows the Actions you hold. When the app runs one, Contro1 allows it, refuses it, or waits for a person first, as your organization's policy says.
| What you see | What to do |
|---|---|
| Grok Bot has no screen for a custom connector, or will not save it | Some plans, or only an admin, may add custom connectors in Grok Bot. Ask your workspace admin. |
| whoami names somebody else | The sign-in was approved with another Contro1 account. Disconnect Contro1 in Grok Bot and connect again, signing in with the intended account. |
| It can only read and preview, or says EXECUTE_SCOPE_REQUIRED | The sign-in was approved with "Run Actions as you" unchecked. Disconnect Contro1 in Grok Bot and connect again with it checked. |
| list_actions is empty | You hold no Actions yet. An administrator allows the application's tools for the organization under Apps, and Actions are given in Access. |
| The sign-in is refused | Contro1 refuses a sign-in that returns to the same computer (a 127.0.0.1 or app-specific address), because the person approving is often on another device. |
No. Connecting grants nothing by itself. Grok Bot can use only the Actions you hold: Apps allows an application's tools for the organization, and Access gives them to people and agents.
You, the person who approved the sign-in. On Agents it appears as "Cursor (signed in as you)", and every call it makes is recorded as yours.
No. You sign in to Contro1 on a Contro1 page, and Grok Bot receives an OAuth token for Contro1. Your password stays with xAI.
Remove the Contro1 connector in Grok Bot. To revoke it from Contro1's side, open Settings > Connected apps.
Contro1 unifies policy, approval and audit for governed Actions across Grok and other agents, and securely manages organizational skills.
Connect Claude Duet to Contro1: add one MCP address, approve the sign-in, and it acts as you, with every call checked and recorded.
Connect OpenAI Dots to Contro1: add one MCP address, approve the sign-in, and it acts as you, with every call checked and recorded.
Choose the applications your organization approves, decide who may do what, and connect one MCP. Every person and agent gets exactly their access, and every action is recorded on their name.