# persist_registry

Registry run key persistence. Auto-selects client.

Agent View of the PolicyLayer registry record for `persist_registry`. HTML page: https://policylayer.com/tools/0xyg3n-claude-c2/persist-registry

## Facts

- Tool: `persist_registry`
- Server: Claude C2 (`0xyg3n/claude-c2`) — https://policylayer.com/tools/0xyg3n-claude-c2.md
- Homepage: https://github.com/0xyg3n/claude-c2
- Risk category: Execute (High risk)
- Registry record: grade F, 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": "persist_registry",
    "arguments": {}
  }
}
```

## Why persist_registry is rated High

This tool modifies Windows registry run keys to establish persistence—a technique that executes code on system startup. While it involves writing to the registry (Write category), it fundamentally achieves code execution and persistence installation (Execute category).

From the tool's own definition: "Tool name 'persist_registry' combined with description 'Registry run key persistence' indicates execution of persistence mechanisms via Windows registry modification. The phrase 'Auto-selects client' suggests autonomous operation on remote systems."

## Use case

AI agents invoke persist_registry to trigger actions in Claude C2. 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 Claude C2:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "persist_registry": {
      "limits": [
        {
          "counter": "persist_registry_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Claude C2 (93)

- `kill` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/kill.md
- `mv` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/mv.md
- `persist_remove` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/persist-remove.md
- `reg_delete` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/reg-delete.md
- `rm` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/rm.md
- `timestomp` — Destructive — https://policylayer.com/tools/0xyg3n-claude-c2/timestomp.md
- `amsi_bypass` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/amsi-bypass.md
- `bypassuac` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/bypassuac.md
- `defender_exclude` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/defender-exclude.md
- `etw_patch` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/etw-patch.md
- `execute_assembly` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/execute-assembly.md
- `firewall_rule` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/firewall-rule.md
- `generate_payload` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/generate-payload.md
- `get_payload` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/get-payload.md
- `getsystem` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/getsystem.md
- `inject` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/inject.md
- `keylog_start` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/keylog-start.md
- `keylog_stop` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/keylog-stop.md
- `mcp_add_tool` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/mcp-add-tool.md
- `mcp_append_code` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/mcp-append-code.md
- `mcp_restart` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/mcp-restart.md
- `mimikatz` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/mimikatz.md
- `persist_schtask` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/persist-schtask.md
- `persist_service` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/persist-service.md
- `persist_startup` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/persist-startup.md
- `persist_wmi` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/persist-wmi.md
- `portscan` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/portscan.md
- `powershell` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/powershell.md
- `privesc_check` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/privesc-check.md
- `psexec` — Execute — https://policylayer.com/tools/0xyg3n-claude-c2/psexec.md
- …and 63 more: https://policylayer.com/tools/0xyg3n-claude-c2.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=0xyg3n-claude-c2 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xyg3n-claude-c2