check_docker_api

Check Docker daemon REST API availability via GET /_ping. Port 2375 = unencrypted, 2376 = TLS. Returns daemon version info from the response headers.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-docker-api.md

WHAT IT DOES

What check_docker_api does on Mcp Nettools

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

RISK

Why check_docker_api is rated Low

This is a diagnostic read operation that retrieves information about a Docker daemon's availability and version. While the ability to probe Docker APIs could inform an attacker about infrastructure, the tool itself only reads status information (GET request to /_ping endpoint) without executing commands, modifying state, or triggering destructive actions.

From the tool's definition Tool performs a GET /_ping request to check Docker daemon API availability and retrieve version info from response headers. No modification, deletion, or execution of code/commands occurs—only querying of daemon status and metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_docker_api safely

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

check_docker_api Allowed

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

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

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

FAQ

Questions about check_docker_api

What does the check_docker_api tool do? +

Check Docker daemon REST API availability via GET /_ping. Port 2375 = unencrypted, 2376 = TLS. Returns daemon version info from the response headers. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_docker_api? +

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

What risk level is check_docker_api? +

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

Can I rate-limit check_docker_api? +

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

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

check_docker_api is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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