Skip to content

Commit fa81308

Browse files
committed
add mcp security info
1 parent b123485 commit fa81308

File tree

1 file changed

+31
-0
lines changed
  • content/manuals/ai/mcp-catalog-and-toolkit

1 file changed

+31
-0
lines changed

content/manuals/ai/mcp-catalog-and-toolkit/toolkit.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,37 @@ The Docker MCP Toolkit enables seamless setup, management, and execution of cont
2121
2222
![Visualisation of the MCP toolkit](/assets/images/mcp_servers.png)
2323

24+
## Security
25+
26+
The Docker MCP Toolkit combines passive and active measures to reduce attack
27+
surfaces and ensure safe runtime behavior.
28+
29+
### Passive security
30+
31+
- Image signing and attestation: All MCP server images are built by Docker and digitally
32+
signed to verify their source and integrity. Each image includes a Software
33+
Bill of Materials (SBOM) for full transparency.
34+
35+
### Active security
36+
37+
Security at runtime is enforced through resource and access limitations:
38+
39+
- CPU allocation: MCP tools are run in their own container. They are
40+
restricted to 1 CPU, limiting the impact of potential misuse of computing
41+
resources.
42+
43+
- Memory allocation: Containers for MCP tools are limited to 2 Gb.
44+
45+
- Filesystem access: By default, MCP Servers have no access to the host filesystem.
46+
Only select servers are explicitly granted file mounts.
47+
48+
- Outbound network access: Network is access is disabled when a server has access to the
49+
filesystem, and vice-versa. Most servers require access to only a single host, port,
50+
and protocol. These permissions are explicitly listed and enforced.
51+
52+
- Interception of tool requests: Requests to and from tools that contain sensitive
53+
information such as secrets are blocked.
54+
2455
## Install an MCP server
2556

2657
To install an MCP server:

0 commit comments

Comments
 (0)