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)
This record as markdown: /tools/onesi-genesis-mcp/henry-replayrun.md
What henry_replayRun does on Genesis
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_id | string | Yes |
Parameters from the server's own tool schema.
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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs henry_replayRun safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For henry_replayRun, this is the rule to start with:
henry_replayRun stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every henry_replayRun call is checked against it from then on.
Questions about 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). It is categorised as a Execute tool in the Genesis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
henry_replayRun accepts 1 parameter: run_id. Required: run_id. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for henry_replayRun: 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 Genesis. Nothing to install.
henry_replayRun is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the henry_replayRun 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.
Set action: deny in the PolicyLayer policy for henry_replayRun. 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.
henry_replayRun is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue