AI agents call diff to retrieve information from Pepper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name alone, 'diff' typically performs comparisons without modifying state. Within the Pepper context of viewing and inspecting iOS Simulator apps, this would be a read-only operation to compare UI elements or states. However, confidence is reduced due to the empty description—it could theoretically do something else.
From the tool's definition Tool name is 'diff'. No description provided. In the context of Pepper (iOS Simulator inspection), a 'diff' tool most likely compares two UI states or objects for inspection purposes.
Documented attack patterns abuse exactly the kind of access diff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pepper, and nothing reaches the server without passing your rules. This is the rule we recommend for diff:
{
"version": "1",
"default": "deny",
"tools": {
"diff": {}
}
}diff is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
diff. It is categorised as a Read tool in the Pepper MCP Server, which means it retrieves data without modifying state.
Register the Pepper 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 Pepper. 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 Pepper MCP server (skwallace36/pepper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Pepper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Pepper tools catalogued and risk-classified — across an index of 42,500+ MCP servers.