Controlling tool access

Choose which of a connector's tools the assistant is allowed to call.

Connecting a server doesn't have to mean handing over everything on it. Each connector lists its tools grouped by what they do, and you decide which groups (or which individual tools) the assistant may call.

This matters most when one MCP server serves two purposes. If you already run an MCP internally, you can connect that same server and still expose only the parts that make sense for a shopper: product discovery, cart, checkout, and nothing else.

The three groups

Tools are sorted for you, by what calling them does:

Group	What's in it
Write tools	Anything that changes state when the assistant calls it: creating a cart, completing a checkout.
Read-only tools	Anything that only fetches: searching the catalogue, looking up an order.
Other tools	Whatever fits neither: tools whose effect isn't declared as one or the other.

Setting access

Open Connectors, select a connector in the list, and its tools appear on the right.

Per group: each group header has Allow and Disallow. This is the setting most merchants use: allow read-only, disallow write, done.

Per tool: each tool has Allow, Default and Disallow. Default means inherit the group, and it's how every tool starts. Set a tool to Allow or Disallow and it stops following its group, which is how you allow one write tool without allowing the rest.

A group showing the grey DEFAULT badge is still at its original value. The badge is telling you nothing has been overridden here yet.

A worked example

A merchant runs one MCP internally for their ops team and connects it to GreatStore too. The shopping agent should be able to find products and build a cart, but must never touch refunds or inventory adjustments, both of which live on the same server.

1. Disallow Write tools at the group level. Everything that mutates is now off.

2. Set Create cart, Update cart and Complete checkout to Allow individually.

The assistant can now shop, and the refund tool sitting beside them is unreachable.

Disallowing read-only tools is what usually breaks an assistant: those are the ones it searches your catalogue with. If answers suddenly go vague, check here before anything else.

WebMCP is group-level only

WebMCP tools are published by the page at runtime, so there's no fixed list to configure ahead of time, only the three group settings. A page-defined tool is offered to the assistant only when its group is set to Allow.