log-graph

Returns visual branch topology as structured data. Wraps

SERVERDocker SOURCE@paretools/docker

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-docker/log-graph.md

WHAT IT DOES

What log-graph does on Docker

AI agents call log-graph 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.

RISK

Why log-graph is rated Low

This tool retrieves and displays historical data (branch topology) without creating, modifying, deleting, or executing any operations. It has no side effects and presents information only, fitting the Read category with low severity due to minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'log-graph' and description indicate it 'Returns visual branch topology as structured data' — a query/retrieval operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log-graph 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 log-graph, this is the rule to start with:

log-graph Allowed

log-graph is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log-graph": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every log-graph call is checked against it from then on.

FAQ

Questions about log-graph

What does the log-graph tool do? +

Returns visual branch topology as structured data. Wraps. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on log-graph? +

Register the Docker MCP server in PolicyLayer and add a rule for log-graph: 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.

What risk level is log-graph? +

log-graph is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit log-graph? +

Yes. Add a rate_limit block to the log-graph 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.

How do I block log-graph completely? +

Set action: deny in the PolicyLayer policy for log-graph. 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.

What MCP server provides log-graph? +

log-graph 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.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 202 Docker tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →