docker/docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-10-28 07:15:09 +03:00
Code Activity

docs: clarify sandbox MCP policy scope

Browse Source 
MCP access guidance could imply that blocking a server prevents every connection from a sandbox. Clarify that MCP policy governs the Docker gateway path, while network policy governs direct outbound MCP connections.
This commit is contained in:
David Karlsson
2026-08-12 07:32:49 +00:00
parent 2712b53a37
commit bf83e830f9
2 changed files with 16 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
content/manuals/ai/sandboxes/governance/access-controls/mcp.md
View File

@@ -2,7 +2,7 @@
title: MCP access policies
linkTitle: MCP access
weight: 50
description: Use Cedar-based MCP policies to control sandbox MCP server registration, tool calls, prompts, resources, and approval gates.
description: Use Cedar-based policies to control MCP server registration and activity routed through the Docker Sandboxes MCP gateway.
keywords: docker sandboxes, MCP policy, MCP access, Cedar policy, requireApproval, AI Governance
---
@@ -13,6 +13,14 @@ withdraw access to a server, require approval for tool calls, and restrict
host-run servers. To register MCP servers and connect them to sandboxes, see
[MCP gateway](../../mcp-gateway.md).
MCP access policies apply only to server registration and requests handled by
Docker's MCP gateway. They don't govern an MCP server that an agent or MCP
client configures and connects to directly from inside the sandbox. A direct
connection to a remote MCP server is outbound sandbox traffic, so
[network access policy](network.md) determines whether the sandbox can reach
the server. To prevent access through both paths, block the server in MCP
access policy and block its network destination in network access policy.
Unlike [network access policies](network.md) and
[filesystem access policies](filesystem.md), MCP policies are organization
policies written in Cedar. Docker defines the `MCP` namespace, including the

7
content/manuals/ai/sandboxes/governance/access-controls/network.md
View File

@@ -59,3 +59,10 @@ organization or to selected teams. For setup steps and team scoping, see
Use [Monitoring policies](../monitor-and-enforce/monitoring.md) to inspect
which network rules are active on a developer machine.
> [!NOTE]
> To manage Model Context Protocol (MCP) server registration and requests
> through Docker's MCP gateway, use [MCP access policies](mcp.md). These
> policies apply only to the gateway. Direct MCP connections from a sandbox
> don't use the gateway, but you can control access to remote MCP servers with
> network policy.