pr-diff
Returns file-level diff statistics for a pull request. Use full=true for patch/hunk content, or nameOnly=true for just the changed file paths.
This record as markdown: /tools/io-github-dave-london-npm/pr-diff.md
What pr-diff does on Npm
AI agents call pr-diff to retrieve information from Npm without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pr-diff is rated Low
This is a pure read operation that retrieves diff information from a pull request. It has no side effects, does not execute code, does not modify data, and does not delete anything. The options allow controlling the verbosity of the read (full content vs. names only), but the operation remains purely informational.
From the tool's definition The tool 'Returns file-level diff statistics for a pull request' with options for 'patch/hunk content' or 'just the changed file paths' — it retrieves and queries data without modifying anything.
Attacks that exploit this kind of access
The rule that runs pr-diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-diff, this is the rule to start with:
pr-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 Npm, apply this rule, and every pr-diff call is checked against it from then on.
Questions about pr-diff
Returns file-level diff statistics for a pull request. Use full=true for patch/hunk content, or nameOnly=true for just the changed file paths. It is categorised as a Read tool in the Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm MCP server in PolicyLayer and add a rule for pr-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 Npm. Nothing to install.
pr-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 pr-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 pr-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.
pr-diff is provided by the Npm 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 Npm, and thousands of servers like it.
This server
Across the catalogue