Check Docker container status in working directory
AI agents call ssh_docker_status to retrieve information from MCP SSH Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and reports the status of Docker containers, which is a read-only query operation with no side effects. It does not start, stop, or modify containers.
From the tool's definition Check Docker container status in working directory
Attacks that exploit this kind of access
Check Docker container status in working directory. It is categorised as a Read tool in the MCP SSH Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SSH Server MCP server in PolicyLayer and add a rule for ssh_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 MCP SSH Server. Nothing to install.
ssh_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 ssh_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 ssh_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.
ssh_docker_status is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →