diff

Part of the Leapfrog MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use diff to create or modify resources in Leapfrog. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON DIFF

Without a policy, an AI agent could call diff repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Leapfrog.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-anthonybono21-cloud-leapfrog.yaml

tools:
  diff:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Leapfrog policy for all 37 tools.

// DETAILS

Tool Name diff

Category Write

MCP Server Leapfrog MCP Server

Risk Level Medium

// MORE LEAPFROG TOOLS

Destructive network_intercept Destructive profile_delete Destructive session_destroy Execute batch_actions Execute execute Execute navigate Execute wait_for Execute wait_for_human

View all 37 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like diff have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the diff tool do? +

Compare the current page state against the last snapshot for this session. Returns only what changed (additions, removals, changes) — massive token savings vs a full re-snapshot. Use after 'act' instead of 'snapshot' when you just need to see what changed. On first call (no previous snapshot), returns the full snapshot with a note. Use 'selector' to scope the diff to a page region.. It is categorised as a Write tool in the Leapfrog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on diff? +

Add a rule in your Intercept YAML policy under the tools section for diff. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Leapfrog MCP server.

What risk level is diff? +

diff is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit diff? +

Yes. Add a rate_limit block to the diff rule in your Intercept 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.

How do I block diff completely? +

Set action: deny in the Intercept 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.

What MCP server provides diff? +

diff is provided by the Leapfrog MCP server (leapfrog-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

diff

Enforce policies on Leapfrog