Access Control plugin
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.
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.
Where it runs
Configuration
The rules of the grant. One matching rule is enough.
The connection that the rule grants. The console labels this Connection.
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.
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.
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.
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.
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.

