Get recent logs from a Docker container.
AI agents call docker_get_logs to retrieve information from HomeOps MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves log data from a container without modifying, executing, or deleting anything. It is purely informational. The blast radius if misused is minimal—an agent gaining access to logs could potentially learn sensitive information, but cannot directly affect system state or infrastructure. Severity is low because log access alone does not enable destructive or critical actions.
From the tool's definition Tool name 'docker_get_logs' and description 'Get recent logs from a Docker container' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of accessing logs confirm this is a Read operation.
Attacks that exploit this kind of access
Get recent logs from a Docker container. It is categorised as a Read tool in the HomeOps MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HomeOps MCP Server MCP server in PolicyLayer and add a rule for docker_get_logs: 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 HomeOps MCP Server. Nothing to install.
docker_get_logs 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_get_logs 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_get_logs. 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_get_logs is provided by the HomeOps MCP Server MCP server (wolffcatskyy/homeops-mcp). 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 →