Connections: Off, Ask first, Allowed
Every tool a connection offers has one of three settings. Allowed: Cora uses it without asking. Ask first: each call waits for a person to approve it on an approval card. Off: Cora never uses it (D0716). You set it once, on the connection, and it is the same in every mission that uses the connection.
The examples on this page follow an invented bike shop, Kestrel Cycles. Leah is its org admin.
Where you set it
Section titled “Where you set it”Open Connections on the left rail and choose the connection. Its page has a Tool access section.
- Tools come in groups. A catalogue service can name its own groups. Umbraco, for example, has Read content and Save drafts. Any other server gets two groups from its tools’ own hints: Read (“Look things up. Nothing is changed.”) and Make changes (“Anything that can change something on the service.”).
- Each group has one setting. Choose Allowed, Ask first or Off for the whole group.
- Each tool can have its own. Press Show each of the N tools to set tools one by one. A group whose tools have different settings shows Mixed.
A mission does not choose tools. It only switches a connection on or off, or, for a personal connection, its owner shares it or stops sharing it there. When the connection is on in a mission, Cora can use every tool that is not Off, with the setting the connection gives it (D0716).
Read tools and write tools
Section titled “Read tools and write tools”A read tool only looks things up, such as finding a ticket or reading a report. A write tool changes something outside Cora, such as creating a ticket or saving a draft.
- Allowed is for tools you trust Cora to use without asking, such as a search or a lookup.
- Ask first is for anything that changes something. Each call waits for a person’s approval.
- Off is for tools nobody needs. Turn on only what the team uses.
A server can say a tool only reads. That hint puts the tool in the Read group, but it never decides on its own: the setting does (D0131). At Kestrel Cycles, Leah sets find_ticket to Allowed, create_ticket to Ask first and leaves delete_ticket Off.
How each kind of connection starts
Section titled “How each kind of connection starts”New tools do not all start the same way. It depends on who added the connection and how.
| Connection | New tools start as |
|---|---|
| An organisation connection an org admin adds by hand, with Add any MCP server | Off, every tool. An org admin turns on the ones the team needs (D0131). |
| An organisation connection an org admin sets up from the catalogue, such as Umbraco | On. Its read tools are Allowed and its draft tools Ask first, because they always ask (D0684). |
| A personal connection | On and Allowed, because sharing your own connection with Cora is your consent. A tool the catalogue marks always-ask starts as Ask first (D0657, D0716). |
You can change any of these at once in the connection’s Tool access section.
If a server changes a tool’s description, the tool is turned Off until it is set again, so a server cannot quietly change what a tool you approved does (D0131). The tool says “Its description changed, so it is off.” On a personal connection, the owner’s Check again turns it back on.
Approval cards
Section titled “Approval cards”When Cora calls a tool set to Ask first, she stops before the call is made (D0132).
- An approval card goes into the mission chat, with a notice. It shows the tool and exactly what Cora wants to send.
- For an organisation connection, the card goes to the holders of the connection’s approval role. For a personal connection, it goes to the owner, or to the approval role the owner named (D0657).
- The approver presses Approve or Reject. There is no editing. If it is approved, Cora makes the call once. If it is rejected, the call is never made.
An approval nobody answers expires after 48 hours and counts as a reject. See Questions, approvals and choice cards for how cards work in the chat, and Connect an MCP server for the full steps.
Who may choose Allowed
Section titled “Who may choose Allowed”Only the person who sets a connection’s access can choose Allowed (D0716).
- An organisation connection: org admins only.
- A personal connection: its owner only. An org admin cannot change it, but can stop sharing it in a mission or remove it (D0647).
Everyone else sees the settings read only, with the line “Only organisation admins can change access. For a personal connection, its owner sets it.” Choosing Allowed or Ask first also needs MCP to be on for the organisation, with the Use MCP servers switch in Settings, Permissions (D0315).
Tools that always ask
Section titled “Tools that always ask”Some tools always wait for an approval card, whatever anyone sets. The catalogue marks them always-ask. Today these are Umbraco’s draft tools, because a draft goes to your public website (D0684).
- Allowed is not offered for an always-ask tool, or for a group that holds one.
- If someone asks for Allowed anyway, the platform refuses it.
- This holds on a personal connection too.
The other way round, a tool the catalogue marks as a read is never offered Ask first: when it is on, it is Allowed.
Related pages
Section titled “Related pages”- Connect an MCP server: adding a server by its address.
- Connect with the service’s sign-in: connecting a service by signing in to it.
- Personal connections: your own connections and sharing them in missions.
- Roles and approvals: how an approval role reaches a person.