diff
Returns file-level diff statistics as structured data. Use full=true for patch content.
This record as markdown: /tools/io-github-dave-london-pare-test/diff.md
What diff does on Test
AI agents call diff 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 diff is rated Low
This tool queries and returns diff information without modifying files, code, or system state. It is purely informational, comparable to running `git diff` or `diff` commands to view changes. The optional full parameter expands the output but does not change the read-only nature. No side effects, reversible operations, code execution, deletions, or financial actions are involved.
From the tool's definition Tool description states it 'Returns file-level diff statistics as structured data' with an optional parameter for 'patch content'.
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 Test, 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 Test, 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 Test MCP Server, which means it retrieves data without modifying state.
Register the Test 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 Test. 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 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