// SCAN REPORT

ContainerGuard MCP

9 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 4 Jul 2026

3 can modify or destroy data

6 read-only

9 tools total

Community server · catalogue entry verified 04/07/2026

How to control ContainerGuard MCP ↓

TOOL MAP

What ContainerGuard MCP exposes to your agents

Read (6) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous ContainerGuard MCP tools

Execute · High execute_command This tool executes code/commands in a containerized environment via the Docker/SSH backend. Execute · High connect_docker Establishing a connection to a remote Docker daemon initiates an active network session and enables subsequent control over containerized workloads. Execute · High connect_ssh Establishing an SSH connection to a remote host is an active external operation that opens a persistent channel to a remote system.

3 of ContainerGuard MCP's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control ContainerGuard MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and ContainerGuard MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check_container_security": {
    "limits": [
      {
        "counter": "check_container_security_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register ContainerGuard MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CONTAINERGUARD →

Instant setup, no code required.

FULL CATALOGUE

All 9 ContainerGuard MCP tools

EXECUTE 3 tools

Execute connect_docker 连接到远程Docker守护进程 Execute connect_ssh 通过SSH连接到远程主机 Execute execute_command 在容器中执行命令

READ 6 tools

Read check_container_security 全面检查容器安全性 Read get_container_logs 获取指定容器的日志 Read get_container_stats 获取容器资源使用统计 Read get_system_info 获取容器系统信息 Read list_containers 获取容器列表（包括停止的容器） Read security_analysis 对容器进行安全分析

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about ContainerGuard MCP

Is the ContainerGuard MCP server safe to use without restrictions? +

The ContainerGuard MCP server is primarily read-only with 6 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the ContainerGuard MCP server expose? +

9 tools across 3 categories: Execute, Read, Write. 6 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on ContainerGuard MCP? +

Register the ContainerGuard MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every ContainerGuard MCP tool call.

Deterministic rules across all 9 ContainerGuard MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CONTAINERGUARD →

Instant setup, no code required.

9 ContainerGuard MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.