log-graph
Returns visual branch topology as structured data. Wraps
This record as markdown: /tools/io-github-dave-london-pare-test/log-graph.md
What log-graph does on Test
AI agents call log-graph to retrieve information from Test without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why log-graph is rated Low
This tool queries and returns structured data about branch topology (likely from a git repository) for visualization purposes. It performs a read-only retrieval of metadata with no side effects, capability to modify data, execute code, destroy data, or commit financial transactions. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool 'log-graph' 'Returns visual branch topology as structured data' - retrieves and presents existing version control information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs log-graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, 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 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 Test, apply this rule, and every log-graph call is checked against it from then on.
Questions about log-graph
Returns visual branch topology as structured data. Wraps. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.
Register the Test 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 Test. Nothing to install.
log-graph 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 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.
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.
log-graph is provided by the Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Test, and thousands of servers like it.
This server
Across the catalogue