docker_unhealthy

Return containers that are exited, restarting, unhealthy, or missing health checks.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/docker-unhealthy.md

WHAT IT DOES

What docker_unhealthy does on Mcp Control Plane

AI agents call docker_unhealthy to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why docker_unhealthy is rated Low

This tool queries the state of Docker containers and returns status information. It performs a read-only operation that retrieves existing data about container health without modifying, executing against, or deleting any containers. No side effects or irreversible actions are possible from its use.

From the tool's definition Tool name is 'docker_unhealthy' and description states it 'Return containers that are exited, restarting, unhealthy, or missing health checks.' The verb 'Return' indicates data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_unhealthy safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_unhealthy, this is the rule to start with:

docker_unhealthy Allowed

docker_unhealthy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_unhealthy": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every docker_unhealthy call is checked against it from then on.

FAQ

Questions about docker_unhealthy

What does the docker_unhealthy tool do? +

Return containers that are exited, restarting, unhealthy, or missing health checks. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_unhealthy? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for docker_unhealthy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Control Plane. Nothing to install.

What risk level is docker_unhealthy? +

docker_unhealthy is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit docker_unhealthy? +

Yes. Add a rate_limit block to the docker_unhealthy rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block docker_unhealthy completely? +

Set action: deny in the PolicyLayer policy for docker_unhealthy. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides docker_unhealthy? +

docker_unhealthy is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →