> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/connectors/tool-access.md).

# Controlling tool access

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.

{% embed url="<https://vimeo.com/1217104150>" %}
Disallowing a whole group, then allowing one tool back
{% endembed %}

<figure><img src="/files/joXrCd9GM7usOsBmTCuq" alt="A connector&#x27;s tools grouped into Write tools and Read-only tools, each with Allow and Disallow controls"><figcaption><p>Shopify MCP's tools, grouped by what they do</p></figcaption></figure>

## 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.

{% hint style="info" %}
A group showing the grey `DEFAULT` badge is still at its original value. The badge is telling you nothing has been overridden here yet.
{% endhint %}

## 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.

{% hint style="warning" %}
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.
{% endhint %}

## WebMCP is group-level only

[WebMCP](/maker-greatstore/connectors/webmcp.md) 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-greatstore/connectors/tool-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.