Low Risk

get_diff_preview

Generate a diff preview showing what changes would be made without applying them. Supports unified, inline (character-level), and side-by-side formats.

How to control get_diff_preview ↓

What get_diff_preview does on OODA Computer Control

AI agents call get_diff_preview to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_diff_preview needs a policy

get_diff_preview performs a read operation that retrieves and displays a diff visualization. It explicitly does not modify, execute, or delete anything - it only previews potential changes in various formats (unified, inline, side-by-side). This is a safe inspection tool with no side effects.

From the tool's definition Tool generates a preview of changes 'without applying them' - this is explicitly non-destructive and read-only. The description states it shows 'what changes would be made' rather than actually making them.

Documented attack patterns abuse exactly the kind of access get_diff_preview gives an agent:

How to control get_diff_preview

PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for get_diff_preview:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_diff_preview": {}
  }
}

get_diff_preview is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OODA Computer Control — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_diff_preview

What does the get_diff_preview tool do? +

Generate a diff preview showing what changes would be made without applying them. Supports unified, inline (character-level), and side-by-side formats. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_diff_preview? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for get_diff_preview: 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 OODA Computer Control. Nothing to install.

What risk level is get_diff_preview? +

get_diff_preview is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_diff_preview? +

Yes. Add a rate_limit block to the get_diff_preview 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.

How do I block get_diff_preview completely? +

Set action: deny in the PolicyLayer policy for get_diff_preview. 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 get_diff_preview? +

get_diff_preview is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.