Skip to content
WeaversDocs
Browse documentation

Weavers / MCP documentation

Permissions & control

Understand Weavers MCP permissions, private data access, reviewable writes, and disconnecting.

Access follows your account

  • Every tool call requires an authenticated connection, its matching permission, and access to the requested resource.
  • Seeing a tool in discovery does not grant permission to use it. Tool names and input schemas can be discovered before sign-in; account data cannot.
  • Your assistant receives the data returned by a tool. Check your assistant provider's data-handling settings before sharing private source or dataset samples.

What each permission allows

  • A permission (also called a scope) authorizes one category of work.
PermissionAllows
weavers.profile.readRead your opaque connection identifier.
weavers.notebooks.readList notebook titles and metadata.
weavers.experiments.readRead facts for experiments you can view.
weavers.strategies.readRead owned project identity, revisions and dataset metadata.
weavers.python_source.readRead private Python source in bounded chunks.
weavers.datasets.previewRead up to ten rows from an owned dataset version.
weavers.experiment_drafts.writeCreate a reviewable experiment draft.
weavers.python_source.proposeStore replacement source for the owner to review.

You review drafts and proposals in Weavers

  • prepare_python_experiment_draft saves a draft with exact source and dataset versions. Finish its settings in Weavers before starting an experiment.
  • propose_python_source stores suggested code. Compare and apply it in Weavers to update the live source file.
  • These tools cannot start an experiment, place an order, or directly apply a source proposal.
  • Read-only access does not include these write permissions. Older connections may need fresh consent for additional permissions.

Disconnect an assistant

  • Open AI connections in Weavers and select Disconnect beside the relevant assistant.
  • The next tool call rechecks the grant and is blocked. An already-running request may finish.
  • Disconnecting does not remove existing drafts, proposals, or the assistant's earlier conversation history.
  • To reconnect, complete authorization again. Tokens issued before the new grant cannot restore access.