reflog
Returns reference log entries as structured data, useful for recovery operations. Also supports checking if a reflog exists.
This record as markdown: /tools/io-github-dave-london-docker/reflog.md
What reflog does on Docker
AI agents call reflog to retrieve information from Docker without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why reflog is rated Low
This tool performs a read-only query of reference log data. It retrieves information useful for recovery operations but does not execute commands, modify data, delete records, or perform financial transactions. The use of 'reflog' in version control (e.g., git reflog) is fundamentally a log inspection mechanism, confirming its Read category classification.
From the tool's definition Tool 'reflog' returns reference log entries as structured data and checks if a reflog exists. The description emphasizes data retrieval ('returns', 'checking if') with no modification or deletion capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs reflog safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reflog, this is the rule to start with:
reflog 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 Docker, apply this rule, and every reflog call is checked against it from then on.
Questions about reflog
Returns reference log entries as structured data, useful for recovery operations. Also supports checking if a reflog exists. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.
Register the Docker MCP server in PolicyLayer and add a rule for reflog: 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 Docker. Nothing to install.
reflog 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 reflog 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 reflog. 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.
reflog is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue