docker_health

Check if Docker daemon is reachable.

SERVERAgent Jail SOURCEidiscoord13-sketch/agent-jail-mcp

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/agent-jail-mcp/docker-health.md

WHAT IT DOES

What docker_health does on Agent Jail

AI agents call docker_health to retrieve information from Agent Jail 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_health is rated Low

Even though docker_health only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_health safely

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

docker_health Allowed

docker_health 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_health": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Jail, apply this rule, and every docker_health call is checked against it from then on.

FAQ

Questions about docker_health

What does the docker_health tool do? +

Check if Docker daemon is reachable. It is categorised as a Read tool in the Agent Jail MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_health? +

Register the Agent Jail MCP server in PolicyLayer and add a rule for docker_health: 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 Agent Jail. Nothing to install.

What risk level is docker_health? +

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

Can I rate-limit docker_health? +

Yes. Add a rate_limit block to the docker_health 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_health completely? +

Set action: deny in the PolicyLayer policy for docker_health. 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_health? +

docker_health is provided by the Agent Jail MCP server (idiscoord13-sketch/agent-jail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Jail, and thousands of servers like it.

This server

All 35 Agent Jail tools →

Across the catalogue

The MCP Attack Database →

Guides

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