# BetterShield Hub assistants: connect, limit and review across sites

Connect an AI assistant to BetterShield Hub once, limit which sites and tools it gets, and see what each site reports. Includes what Hub cannot change.

By M Asif Rahman, Nov 21, 2026.

To connect an AI assistant to many WordPress sites, connect it once to **BetterShield Hub** from **Agents › Connect** and then narrow what it can reach with **Limits**. The assistant gets one workspace connection for the sites its owner can already see, and Hub reads what each site reports about its own safeguards. Hub does not change a site’s connections: to revoke one, you open WordPress. This guide covers the Hub side, what it shows and what it leaves to the site.

If you are setting up one site first, [AI agents on a WordPress site: a team setup routine](/blog/wordpress-ai-agents-team-setup/) walks through the site’s own switches, and [WordPress MCP permissions: limit each AI app’s tools](/blog/wordpress-mcp-tool-limits/) covers the per-app tool list on a site. This post is about the Hub layer on top: one connection, many sites, and the limits that keep it small.

## Quick summary

- **Agents › Connect** in Hub gives an assistant one workspace connection to the sites its owner can access.
- **Limits** narrow the owner’s role: **Read only**, **Only these sites**, and a per-tool selection. They never grant access the person does not already have.
- An agent that cannot open a browser can register itself through Hub’s connection instructions, and you approve it in your own browser.
- The **Connections and safeguards** card on a site shows what that site reports, and tells you when the report is stale.
- Revoking a site’s own connection, or changing its safeguards, happens in WordPress, not in Hub.

## Why a Hub connection helps

On one site, an assistant is connected from **BetterShield › Agents** in WordPress, and the site’s own switches decide what it may read or change. That is the right place to start. With a handful of sites, repeating that on each one gets tedious and easy to get wrong.

Hub is the free dashboard that lists your connected sites in one workspace. Connecting an assistant to Hub means one connection and one set of limits for the sites that person can see. The [Model Context Protocol](https://en.wikipedia.org/wiki/Model_Context_Protocol) is the open standard assistants use to call tools on a service like Hub, and the limits below shape which tools and which sites that connection is offered.

Two things stay true. The workspace role and site permissions of the person who connects still apply, and the connection can only be narrower than that. And the site keeps its own records: Hub reports what a site says, so a stale or missing report is shown as stale or missing.

## What Hub shows and what it leaves to the site

| Where | What you can do | What it cannot do |
|---|---|---|
| **Agents › Connect** in Hub | Connect an assistant, set **Limits**, **Disconnect** | Give the assistant more than its owner’s role |
| **Connections and safeguards** card on a site | Read the site’s connections and its read, change and activity-recording safeguards | Revoke the site’s own connection or change its safeguards |
| WordPress, **BetterShield › Agents** | Revoke a site-level connection, change safeguards | Change another site |

The card on a site reports connections separately from the assistants connected to the workspace. A site-level connection is one the site itself recognizes. A workspace connection is one you made in Hub. They answer different questions, so check both when you are finding out who can reach a site.

## Connect an assistant to Hub

### Set it up

1. Sign in to your free [BetterShield Hub](/bettershield-hub/) account. Your workspace role and site permissions decide what you can see and do.
2. Open **Agents › Connect**.
3. Under **Choose an assistant**, select the product. The screen offers **Claude**, **ChatGPT**, **Claude Code**, **Cursor**, **VS Code**, **Windsurf**, **opencode** and **Other**. **Claude** is selected by default.
4. Follow the instructions shown for that assistant and copy its address, command or configuration where asked. Choose **Other** for a client that supports remote HTTP MCP and browser sign-in through OAuth.
5. Finish the connection in the assistant and approve it on Hub’s sign-in page.
6. Under **Connected assistants**, open **Limits**.

[Connect an assistant to Hub](/docs/hub-assistant-connections/) has the screen in full. A fixed token field by itself does not work, because the connection needs the OAuth browser sign-in or the self-registration flow below.

## Set the limits

Under **Connected assistants**, **Limits** has three controls:

| Limit | What it does | Default |
|---|---|---|
| **Read only** | Blocks any change through that connection | Off |
| **Only these sites** | Narrows the connection to the sites you choose | Every site its person sees |
| Tool selection | Clear a tool to stop the assistant being offered it | Every offered tool allowed |

A blocked tool is not listed to the assistant, and a direct call to it is refused. A site outside **Only these sites** is unavailable to that connection. We recommend starting every new connection read-only, limiting it to the client or project sites it needs, and blocking tools that have nothing to do with its job.

## Connect an agent that cannot open a browser

Some agents cannot complete an OAuth browser sign-in. Hub has a route for them:

1. Give the agent `https://hub.bettershield.ai/auth.md`. Those instructions describe registration, approval, claiming access and token renewal. Ask for read-only access if you only want an assessment.
2. The agent registers and gives you an approval link. It does not need your password or a WordPress credential.
3. Open the link and sign in to Hub if asked. On **Approve an agent**, review its name, the network it registered from, its software description and what it asks to do. Its displayed name is its own claim.
4. Under **The workspace it connects to**, choose the workspace. **Read only** lets you narrow a request for changes if your role allows them. A viewer can approve reading only.
5. Select **Approve**, complete **Confirm it’s you** if asked, and give the six-digit code Hub shows to the agent you started.

An expired request needs a new registration, and five wrong codes end a registration. Do not approve a link you did not expect, and do not pass its code to a different requester. [Approve an agent](/docs/hub-agent-self-connection/) has the screen and the full steps.

## Check what a site reports

Open a connected site in Hub and find **Connections and safeguards**. It lists each connection the site recognizes with a permission summary, and whether the site’s read, change and activity-recording safeguards are available. It can also show that a connection report is stale, so treat a stale message as a reason to refresh before you rely on the list.

There are no Hub defaults here. The card reflects the site’s own **Agents** settings. If a connection has no owner or purpose any more, open WordPress to revoke it. If change access is turned off on the site, Hub can still keep its read access, but it cannot apply plans. [Review a site’s assistant connections in Hub](/docs/hub-site-agents/) has the card in detail.

## Keep the tools Hub needs

A tool selection on the site can interfere with Hub itself. BetterShield 1.1.8 warns before a selection removes Hub’s signed event-link read, or both score reads. Removing them can interrupt Hub’s event link, scores or findings, so read that warning and keep the tools your Hub connection needs before you save. The warning does not grant change access. [Limit the tools of a connected app](/docs/assistant-tool-limits/) explains the list.

On the site, **Test Connection** under **Connection diagnostics** makes one real call and shows how far it got. In 1.1.8 its busy state and completion tick show the test ran, and the result is brought into view. Read the result rather than treating the tick alone as success.

## What it can break, and how to undo

- **Disconnect** on **Connected assistants** ends that connection. It cannot be restored, so connect the assistant again if you removed it by mistake.
- **Read only** or a blocked tool can stop a workflow that needs it. Turn **Read only** off, or select the tool again, to restore it.
- **Only these sites** can leave a site out. Choose the site again under **Limits**.
- An assistant allowed to change sites can request plans and actions within its owner’s role and the site’s own connection permissions. Small reversible fixes may run directly. Sign-in changes, removing a protection and other sensitive actions need the site’s approval plan.
- If a change times out, inspect the site or **Activity** in Hub before asking the assistant to repeat it. The site may still be finishing the first action.

## Check it is working

1. The assistant appears under **Connected assistants**.
2. A test question about an allowed site is answered.
3. A blocked tool is not offered, and a site outside **Only these sites** is unavailable.
4. The **Connections and safeguards** card for each site lists the connections you expect, without a stale message.
5. [Review Hub activity](/docs/hub-activity/) shows the calls the assistant made.

## Recommended settings

We recommend:

- Start every connection **Read only** while you evaluate it.
- Use **Only these sites** for client or project work.
- Block tools unrelated to the assistant’s job, and keep the ones Hub needs.
- Remove connections that no longer have an owner or purpose.
- Keep agent activity recording on for sites where assistants can act.

## Frequently asked questions

### Do I need BetterShield Hub to connect an assistant?

No. A single site can connect an assistant from **BetterShield › Agents** in WordPress with no Hub account. Hub is free and optional, and it helps when one assistant should reach several sites.

### Can a limit give an assistant more access?

No. Limits narrow the owner’s role. They do not grant access the person does not already have.

### Can Hub revoke a site’s own connection?

No. The card on a site shows what the site reports. To revoke a site-level connection or change its safeguards, open WordPress.

### What if my agent cannot open a browser?

Give it Hub’s connection instructions. It registers and gives you an approval link, which you review and approve in your own browser before passing the six-digit code back.

### What happens if I disconnect an assistant by mistake?

**Disconnect** cannot be restored. Connect the assistant again and set its limits once more.

## Conclusion

A Hub connection gives an assistant one way in to the sites its owner can see, and the limits keep that small: read only, named sites and a short tool list. Hub shows what each site reports and leaves revoking a site’s own connection to WordPress. BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/). For the screen in full, see [Connect an assistant to Hub](/docs/hub-assistant-connections/).
