# henry_replayRun

Read every event of a Henry run and fold them into turns: each turn's inputs and the model's answer, plus pending events after the last answer. A turn's number is the turn to pass to henry_forkRun to re-run that answer. (GET /v1/henry/runs/{run_id}/events, all pages)

Agent View of the PolicyLayer registry record for `henry_replayRun`. HTML page: https://policylayer.com/tools/onesi-genesis-mcp/henry-replayrun

## Facts

- Tool: `henry_replayRun`
- Server: Genesis (`@onesi/genesis-mcp`) — https://policylayer.com/tools/onesi-genesis-mcp.md
- Install: `npx -y @onesi/genesis-mcp`
- Homepage: https://www.npmjs.com/package/@onesi/genesis-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `run_id` | string | yes |  |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "henry_replayRun",
    "arguments": {
      "run_id": "<run_id>"
    }
  }
}
```

## Why henry_replayRun is rated High

henry_replayRun 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: Bulk/mass operation — affects multiple targets

## Use case

AI agents invoke henry_replayRun to trigger actions in Genesis. 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 Genesis:

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

## Other tools on Genesis (1126)

- `beacons_deleteDashboardResource` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/beacons-deletedashboardresource.md
- `beacons_revokeBridgeDevice` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/beacons-revokebridgedevice.md
- `blinds_deleteCredential` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/blinds-deletecredential.md
- `blinds_revokeAllCredentials` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/blinds-revokeallcredentials.md
- `blinds_revokeConsent` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/blinds-revokeconsent.md
- `blinds_revokeDelegate` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/blinds-revokedelegate.md
- `boxes_mail_agents_delete` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/boxes-mail-agents-delete.md
- `brews_deleteBrew` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/brews-deletebrew.md
- `brews_uninstallBrew` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/brews-uninstallbrew.md
- `connections_revoke` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/connections-revoke.md
- `dials_deleteNumber` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/dials-deletenumber.md
- `dials_deleteWorkflow` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/dials-deleteworkflow.md
- `fleets_cancelTask` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-canceltask.md
- `fleets_deleteAgent` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-deleteagent.md
- `fleets_deleteComputerConnection` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-deletecomputerconnection.md
- `fleets_deleteConnection` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-deleteconnection.md
- `fleets_deleteWebConnection` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-deletewebconnection.md
- `fleets_killSeat` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-killseat.md
- `fleets_releaseSeat` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/fleets-releaseseat.md
- `flocks_cancelAgent` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-cancelagent.md
- `flocks_deleteAccount` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-deleteaccount.md
- `flocks_resetAccountIdentity` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-resetaccountidentity.md
- `flocks_revokeGrant` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-revokegrant.md
- `flocks_revokeNode` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-revokenode.md
- `flocks_rotateNodeCredential` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/flocks-rotatenodecredential.md
- `foundry_cancelFineTuningJob` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/foundry-cancelfinetuningjob.md
- `foundry_deleteFile` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/foundry-deletefile.md
- `foundry_deleteFineTuningJob` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/foundry-deletefinetuningjob.md
- `foundry_deleteProviderKey` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/foundry-deleteproviderkey.md
- `garden_cancelPayment` — Destructive — https://policylayer.com/tools/onesi-genesis-mcp/garden-cancelpayment.md
- …and 1096 more: https://policylayer.com/tools/onesi-genesis-mcp.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=onesi-genesis-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/onesi-genesis-mcp