AI agents call docker_grep to retrieve information from Log without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation on Docker container logs. It retrieves matching log entries based on regex patterns but does not create, modify, delete, or execute any actions.
From the tool's definition Tool description states 'Search Docker container logs with a regex pattern' - a search operation that retrieves and queries log data without modifying or deleting any data.
Attacks that exploit this kind of access
Search Docker container logs with a regex pattern. It is categorised as a Read tool in the Log MCP Server, which means it retrieves data without modifying state.
Register the Log MCP server in PolicyLayer and add a rule for docker_grep: 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 Log. Nothing to install.
docker_grep 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_grep 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_grep. 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_grep is provided by the Log MCP server (sheikhbasit/log-mcp-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 →