---
schema_version: "1"
id: 33612c47a3e5949801e4bf9af4ac8c4e0d6771fc5bab0b2243eda738548bb5c8
title: MCP Global Access Policy
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.13/policies-included-mcp-global-access.md
canonical_url: https://docs.mulesoft.com/gateway/1.13/policies-included-mcp-global-access
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 681ab64c90261d376e457969119829ad5bd2affb8e8bf667a712ac8cd6f69081
description: MuleSoft Documentation Site
release: "1.13"
latest: false
---
---
product: Omni Gateway
version: 1.13
keywords: api gateway, flex gateway, gateway, policy, mcp, global access
---

# MCP Global Access Policy

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

<table><colgroup><col> <col></colgroup><tbody><tr><td><p><strong>Policy Name</strong></p></td><td><p>MCP Global Access</p></td></tr><tr><td><p><strong>Summary</strong></p></td><td><p>Restricts which MCP tools, resources, and prompts are exposed by defining Allow and Block rules</p></td></tr><tr><td><p><strong>Category</strong></p></td><td><p>MCP</p></td></tr><tr><td><p><strong>First Omni Gateway version available</strong></p></td><td><p>v1.9.3</p></td></tr><tr><td><p><strong>Release Notes</strong></p></td><td><p><a href="https://docs.mulesoft.com/release-notes/gateway/policies/mcp-global-access-release-notes">MCP Global Access</a></p></td></tr><tr><td><p><strong>Returned Status Codes</strong></p></td><td><p>200 with JSON-RPC error code -32008 — Returned when a call targets a blocked tool, resource, or prompt</p></td></tr></tbody></table>

> [!NOTE] This policy supports Model Context Protocol (MCP) version 2025-06-18 and earlier. To learn
> more about MCP, see [MCP Specification](https://modelcontextprotocol.io/specification/2025-06-18).

## Summary

The MCP Global Access policy controls which MCP tools, resources, and prompts are available. Use it
to filter the overall list of MCP capabilities that enter your network.

You define rules to allow or block specific items based on their names (for tools and prompts) or
URIs (for resources). When both Allow and Block rules exist, Block rules always take precedence. The
policy applies to:

- Request authorization: The gateway rejects calls to blocked items with a JSON-RPC error stating
  `Access denied to: <name-or-uri>`:

  - `tools/call` requests

  - `resources/read` requests

  - `prompts/get` requests

- Response filtering: The list returned to the client includes only permitted items:

  - `tools/list` responses

  - `resources/list` responses

  - `prompts/list` responses

Filtering applies to both JSON-RPC and SSE response formats.

## Configuring Policy Parameters

### Omni Gateway Local Mode

The MCP Global Access policy isn’t supported in Local Mode.

### Managed Omni Gateway and Omni Gateway Connected Mode

When you apply the policy from the UI, the following parameters are displayed:

<table><colgroup><col> <col></colgroup><thead><tr><th>Element</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>Rules</p></div></div></td><td><div><div><p>Defines the access control rules. At least one rule is required. Each rule allows or blocks access to matching tools, resources, or prompts.</p></div></div></td></tr><tr><td><div><div><p>Rule</p></div></div></td><td><div><div><p>Defines whether to <strong>Allow</strong> or <strong>Block</strong> access.</p></div></div></td></tr><tr><td><div><div><p>Match type</p></div></div></td><td><div><div><p>Determines how to match the value. Use <strong>literal</strong> for an exact name match or <strong>pattern</strong> for a regular expression.</p></div></div></td></tr><tr><td><div><div><p>Value</p></div></div></td><td><div><div><p>The tool name, resource URI, or prompt name for literal match type, or the regex pattern for pattern match type.</p></div></div></td></tr></tbody></table>

## Rule behavior

Rule order doesn’t matter. The policy evaluates all rules and applies this logic depending on the
combination of rule types are applied:

Only Allow rules

Only items that match at least one Allow rule are permitted. All others are blocked.

Only Block rules

All items are permitted except those that match a Block rule.

Both Allow and Block rules

Only items that match at least one Allow rule and do not match any Block rule are permitted. If an
item matches both an Allow and a Block rule, it is blocked. Items that match no Allow rule are also
blocked.

### Example: Allow list only

To expose only specific tools:

```yaml
rules:
  - rule: Allow
    match_type: literal
    value: get_weather
  - rule: Allow
    match_type: literal
    value: get_user
```

Only `get_weather` and `get_user` can be called. All other tools are blocked and omitted from
`tools/list` responses.

To expose only specific resources by URI pattern:

```yaml
rules:
  - rule: Allow
    match_type: pattern
    value: ^file://public/.*
```

In the previous example, only resources matching the `[file://public/](file://public/)` URI pattern
are exposed and blocks all tools and prompts, since their names don’t match the pattern. To scope by
type, combine allow rules that cover each capability you want to expose:

```yaml
rules:
  - rule: Allow
    match_type: pattern
    value: ^file://public/.*
  - rule: Allow
    match_type: literal
    value: get_user
```

### Example: Block List Only

To block specific tools and allow everything else:

```yaml
rules:
  - rule: Block
    match_type: literal
    value: admin_delete
  - rule: Block
    match_type: literal
    value: get_secret
```

All tools except `admin_delete` and `get_secret` are exposed.

### Example: Allow and Block with Pattern

To allow a family of tools but block one of them:

```yaml
rules:
  - rule: Allow
    match_type: pattern
    value: ^get_.*
  - rule: Block
    match_type: literal
    value: get_secret
```

Tools whose names match the pattern `^get_.*`, such as `get_weather` or `get_user`, are exposed.
`get_secret` is explicitly blocked even though it matches the Allow pattern, because Block takes
precedence.

## See Also

- [MCP Access Control: How the Policies Work Together](https://docs.mulesoft.com/gateway/1.13/policies-mcp-access-control-together)

- [MCP Tool Mapping](https://docs.mulesoft.com/gateway/1.13/policies-included-mcp-tool-mapping)

- [MCP Attribute-Based Access Control](https://docs.mulesoft.com/gateway/1.13/policies-included-mcp-attribute-access-control)

- [Included Policies Directory](https://docs.mulesoft.com/gateway/1.13/policies-included-directory)