Scoped AI Connections in xSpeed Hub
One AI credential does not have to mean full control of everything. In xSpeed Hub, every connection can be scoped: read-only, limited to specific sites, and refused individual tools — so the credential in your AI client carries exactly the power you meant to give it.
What this does
When you mint a connection in the Hub’s Connect panel, an Access section lets you set:
- Read-only — the AI can inspect everything in scope but change nothing.
- Per-site access levels — each site is Full access, Read-only, or No access. It works as a default plus exceptions, so a hundred sites is one decision and a handful of overrides. A site attached after minting inherits the default instead of silently falling outside the credential.
- Denied tools — untick individual tools the connection may never call, whatever else its scope allows.
Leave everything at the default and you get an unrestricted connection in one click, exactly as before.
Editing a live connection
You can tighten (or adjust) a connection’s scope without reconnecting — no new token, no re-pasting config into every AI client. Enforcement re-reads the scope on each request, so an edit lands on the next call.
Rotation is separate, and deliberately so: Rotate is the leaked-token remedy. It mints a fresh secret and kills the old one, and it always preserves the scope — widening a credential during a security response is the worst possible moment, so rotate never does.
How restrictions combine
Restrictions only ever narrow, never widen:
- A connection’s reach is the intersection of its own scope and the minting member’s role. Naming a site in a scope cannot grant access the member does not already have, and a Viewer’s credential can never write, whatever its token says.
- A denied tool is refused even for reads.
- A restricted connection asking about an off-limits site gets the same “no such site” answer as for a site that does not exist — scopes are not an enumeration oracle.
Choosing a scope
| You want the AI to… | Scope to use |
|---|---|
| Monitor and report across the fleet | Read-only, all sites |
| Manage one client’s site and nothing else | Full access on that site, No access default |
| Do everything except destructive purges | Full access, deny the purge tools |
| Everything (your own single-person account) | The one-click default |
Related
- Connecting to xSpeed Hub
- Teams, Roles, and Workspaces in xSpeed Hub
- Connecting AI Agents with the MCP Server