log-graph
Returns visual branch topology as structured data. Wraps
This record as markdown: /tools/io-github-dave-london-pare-search/log-graph.md
What log-graph does on Search
AI agents call log-graph to retrieve information from Search 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 retrieves and returns structured information about branch topology from what appears to be a git repository context. It performs a query operation with no capability to modify, delete, or execute code. The 'log-graph' name and 'structured data' return value indicate a pure data retrieval function. No destructive, financial, or execution capabilities are evident.
From the tool's definition The tool "Returns visual branch topology as structured data" and "Wraps" (description incomplete but indicates a wrapper around query/inspection 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 Search, 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 Search, 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 Search MCP Server, which means it retrieves data without modifying state.
Register the Search 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 Search. 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 Search 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 Search, and thousands of servers like it.
This server
Across the catalogue