> Source: https://wexa.ai/docs/connectors/list-connector-access-scopes

# list-connector-access-scopes

List the access scopes you may give a connector you configure, as the console's connect wizard offers them. Which scopes you may give is bounded by your role, so two callers can get different lists. Needs the `fabric:orchestrate.read` grant.

The shape of `result` for `list-connector-access-scopes` is not recorded here: it was not captured against a live deployment. Call it once and read what comes back rather than assuming a shape.

**List access scopes**

**Wexa MCP server**

```bash
curl -sS -X POST https://fabric.wexa.ai/mcp/$FABRIC_PROJECT_ID \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "Mcp-Session-Id: $MCP_SESSION_ID" \
  -H "content-type: application/json" -H "accept: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list-connector-access-scopes","arguments":{}}}'
```

**REST API**

```bash
curl -sS https://fabric.wexa.ai/v1/list-connector-access-scopes \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'
```

**TypeScript SDK**

```ts
import { Fabric } from '@wexa-fabric/sdk'

const fabric = new Fabric()
const result = await fabric.listConnectorAccessScopes()
```

**Python SDK**

```python
from wexa import Fabric

fabric = Fabric()
out = fabric.list_connector_access_scopes()
```

## Parameters

| Parameter | Type | Required | Notes |
| --- | --- | --- | --- |
| none | | | This tool takes no parameters. Send an empty object. |

**More details**

An access scope decides who may use the connector: `organization`, `department`, `project` or `individual`. See [`list-connectors`](/docs/connectors/list-connectors) for what each one means. The platform's answer is passed on as it is: the scopes you may give, as the console's connect wizard reads them.

Pass one of them to [`configure-connector`](/docs/connectors/configure-connector) as `access_scope`; `configure-connector` enforces the same bound. Not marked consequential.

Every tool call works the same way: [How every tool call works](/docs/sdks-and-apis/how-every-tool-call-works).