docker_status
Get the current status of the Docker/container runtime service.
This record as markdown: /tools/spranab-truenas-mcp/docker-status.md
What docker_status does on Truenas
AI agents call docker_status to retrieve information from Truenas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why docker_status is rated Low
This tool retrieves status information about the Docker service without creating, modifying, deleting, or executing any operations. It is a non-destructive read operation that queries the current state of a system service. The blast radius of misuse is minimal—an attacker could only gain visibility into whether the Docker service is running, which poses no direct risk to data or system integrity.
From the tool's definition Tool name 'docker_status' and description 'Get the current status of the Docker/container runtime service' indicate a query/retrieval operation with no modification of state.
Attacks that exploit this kind of access
The rule that runs docker_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_status, this is the rule to start with:
docker_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every docker_status call is checked against it from then on.
Questions about docker_status
Get the current status of the Docker/container runtime service. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for docker_status: 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 Truenas. Nothing to install.
docker_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the docker_status 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.
Set action: deny in the PolicyLayer policy for docker_status. 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.
docker_status is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue