# binary_patch_preview

Verify disk bytes and preview replacement; retain its token for a copy-on-write apply.

Agent View of the PolicyLayer registry record for `binary_patch_preview`. HTML page: https://policylayer.com/tools/010-editor-mcp/binary-patch-preview

## Facts

- Tool: `binary_patch_preview`
- Server: 010 Editor (`AuroraAeon/010-editor-mcp`) — https://policylayer.com/tools/010-editor-mcp.md
- Homepage: https://github.com/AuroraAeon/010-editor-mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "binary_patch_preview",
    "arguments": {}
  }
}
```

## Why binary_patch_preview is rated Medium

An AI agent can call binary_patch_preview faster than any human can review: one bad instruction and it creates or modifies resources in 010 Editor by the hundred, each call as confident as the last.

## Use case

AI agents use binary_patch_preview to create or update resources in 010 Editor, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 010 Editor environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 010 Editor:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "binary_patch_preview": {
      "limits": [
        {
          "counter": "binary_patch_preview_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 010 Editor (13)

- `editor_run_template` — Execute — https://policylayer.com/tools/010-editor-mcp/editor-run-template.md
- `binary_diff` — Read — https://policylayer.com/tools/010-editor-mcp/binary-diff.md
- `binary_inspect` — Read — https://policylayer.com/tools/010-editor-mcp/binary-inspect.md
- `binary_read` — Read — https://policylayer.com/tools/010-editor-mcp/binary-read.md
- `binary_search` — Read — https://policylayer.com/tools/010-editor-mcp/binary-search.md
- `editor_context` — Read — https://policylayer.com/tools/010-editor-mcp/editor-context.md
- `editor_read` — Read — https://policylayer.com/tools/010-editor-mcp/editor-read.md
- `editor_status` — Read — https://policylayer.com/tools/010-editor-mcp/editor-status.md
- `server_status` — Read — https://policylayer.com/tools/010-editor-mcp/server-status.md
- `binary_patch_apply` — Write — https://policylayer.com/tools/010-editor-mcp/binary-patch-apply.md
- `editor_patch_apply` — Write — https://policylayer.com/tools/010-editor-mcp/editor-patch-apply.md
- `editor_patch_preview` — Write — https://policylayer.com/tools/010-editor-mcp/editor-patch-preview.md
- `editor_select` — Write — https://policylayer.com/tools/010-editor-mcp/editor-select.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=010-editor-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/010-editor-mcp