> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Access Control plugin

> Reference for the Access Control plugin, which grants a consumer access to connections, methods, paths, and MCP tools.

The Access Control plugin grants a consumer access to connections. Each instance is a grant: a list of rules, where each rule names one connection and, optionally, what the consumer may do there. On MCP routes, the plugin also removes the tools that the consumer isn't granted from `tools/list` responses.

> **Note**
>
> On an Enterprise data plane, Access Control needs the OPA policy sidecar, which the Helm chart turns on with `opa.enabled`. Without it, requests to gated connections fail (`502` by default), and requests to open connections still pass. For more information, see [Helm values](/run/helm-values).

## Where it runs

|             |                                          |
| ----------- | ---------------------------------------- |
| Protocols   | HTTP, LLM, MCP, and A2A routes, and gRPC |
| Scope kinds | `consumer`, `service`, `route`           |
| Phase       | Request, and response for MCP tool lists |

## Configuration

**`rules`** `array of objects`

The rules of the grant. One matching rule is enough.

---

**`rules[].service`** `string` — required

The connection that the rule grants. The console labels this **Connection**.

---

**`rules[].methods`** `array of strings`

HTTP methods allowed on HTTP and LLM requests. Matching is exact and case-sensitive. If you leave it out, the rule doesn't limit by this field, as long as the rule sets no field for another protocol.

---

**`rules[].paths`** `array of strings`

Path patterns allowed on HTTP and LLM requests. If you leave it out, the rule doesn't limit by this field, as long as the rule sets no field for another protocol.

---

**`rules[].mcp_tools`** `array of strings`

MCP tool name patterns allowed. If you leave it out, the rule doesn't limit by this field, as long as the rule sets no field for another protocol.

---

**`rules[].grpc_methods`** `array of strings`

gRPC method patterns allowed. If you leave it out, the rule doesn't limit by this field, as long as the rule sets no field for another protocol.

---

**`rules[].a2a_skills`** `array of strings`

A2A skill patterns allowed. If you leave it out, the rule doesn't limit by this field, as long as the rule sets no field for another protocol.

---

In patterns, `*` is the only wildcard and matches any characters, including `/`. Patterns match the whole value and are case-sensitive. `?` and `**` make the grant invalid. The control plane accepts them on save, and the data plane then fails that consumer's requests (`502` under fail-closed). An empty list places no constraint, so a rule that sets only `service` grants the whole connection on every protocol.

## Example

```json
{
  "name": "grant-alice-linear",
  "plugin_id": "access-control",
  "scope": { "kind": "consumer", "name": "alice" },
  "config": {
    "rules": [
      { "service": "linear-mcp", "mcp_tools": ["list_*", "get_issue"] },
      { "service": "billing-api", "methods": ["GET"], "paths": ["/invoices/*"] }
    ]
  }
}
```

## Related guides

* [Manage users](/configure/organization/users)
* [Control traffic with plugins](/configure/plugins)