# editor_run_template

Run a .bt template from a configured trusted root on the intended live buffer.

Agent View of the PolicyLayer registry record for `editor_run_template`. HTML page: https://policylayer.com/tools/010-editor-mcp/editor-run-template

## Facts

- Tool: `editor_run_template`
- 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: Execute (High 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": "editor_run_template",
    "arguments": {}
  }
}
```

## Why editor_run_template is rated High

editor_run_template triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Admin/system-level operation

## Use case

AI agents invoke editor_run_template to trigger actions in 010 Editor. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## 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": {
    "editor_run_template": {
      "limits": [
        {
          "counter": "editor_run_template_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 010 Editor (13)

- `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
- `binary_patch_preview` — Write — https://policylayer.com/tools/010-editor-mcp/binary-patch-preview.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