Skip to content
Resistance Tools
Loading search…
Open app

Permissions and access

Understand scopes, resource restrictions, expiration and revocation.

Browse documentation

MCP access combines the authenticated wallet, granted scopes and any domain or Bag restrictions.

Scope groups

PermissionAllows
wallet:readRead wallet owner/actor context
sites:read, deployments:readInspect sites, content, versions and history
sites:writePublish and manage permitted attachments
sites:rollback, sites:deleteRestore or delete eligible sites
dns:read, subdomains:readRead supported names, items and control state
storage:readInspect Bags, providers, quotes and operations
storage:write, storage:deleteCreate/import or remove platform Bag references
media:writeUpload template images
transactions:requestPrepare a manual wallet confirmation
mcp:read, mcp:revokeInspect access/audit or revoke consent

Resource restrictions

Domain allowlists use exact names and preserve .ton and .t.me namespaces. A parent name is not a wildcard grant for every child. Bag restrictions apply to exact BagIDs.

Resource restrictions also filter the lists returned by tools.

Expiration and refresh

Access tokens last 15 minutes and are normally refreshed by the client. Consent and refresh access last up to 30 days for standard scopes, or 24 hours when sensitive scopes are included. Sensitive scopes include transaction requests, rollback, site/Storage deletion and consent revocation.

The client normally refreshes access automatically. Sign in again when consent expires or is revoked.

Revoke access

Inspect current consents and sessions with mcp.access.list. Revoke the intended consent using its exact confirmation identifier. Revoking the current grant can prevent subsequent reads through that same connection.

Audit tools show redacted events and summaries of the client's requests.

Connection problems

For an unauthorized response, allow the client to refresh its token or sign in again if consent has expired or been revoked. For a forbidden resource, check the granted scopes and exact-name or Bag restrictions.

A resource missing from a tool's list may be excluded by those restrictions.