diff
Returns file-level diff statistics as structured data. Use full=true for patch content.
This record as markdown: /tools/io-github-dave-london-go/diff.md
What diff does on Go
AI agents call diff to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why diff is rated Low
This tool retrieves and displays differences between file versions without modifying, executing, or deleting any data. Even with full=true to include patch content, it remains a read operation that presents information rather than applies changes. The low severity reflects minimal risk if misused by an agent—viewing diffs cannot harm system state.
From the tool's definition Tool description states it 'Returns file-level diff statistics as structured data' with an option for 'patch content'. The verb 'Returns' indicates data retrieval with no modification capability.
Attacks that exploit this kind of access
The rule that runs diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For diff, this is the rule to start with:
diff 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 Go, apply this rule, and every diff call is checked against it from then on.
Questions about diff
Returns file-level diff statistics as structured data. Use full=true for patch content. It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go MCP server in PolicyLayer and add a rule for diff: 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 Go. Nothing to install.
diff 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 diff 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 diff. 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.
diff is provided by the Go 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 Go, and thousands of servers like it.
This server
Across the catalogue