Capture a single point-in-time snapshot of the project dashboard + metrics and append it to the partitioned JSONL file at ~/.ralph-hero/snapshots/<owner>/<projectNumber>.jsonl. Fetches all project items (full project scan, no silent 500-cap) so per-phase WIP and totals reflect every item regardle...
AI agents use ralph_hero__capture_snapshot to create or update resources in Ralph Hero — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ralph Hero environment.
The tool captures a snapshot and appends it to a file. It is a write operation (append-only to a JSONL file) with no destructive or financial implications. Misuse could result in excessive disk usage or spamming of snapshot files, but effects are reversible (files can be deleted). Severity is medium because it writes to the local filesystem and performs a full project scan.
From the tool's definition append it to the partitioned JSONL file at ~/.ralph-hero/snapshots/<owner>/<projectNumber>.jsonl ... Append-only, schema-versioned. Returns the snapshot row that was written.
Attacks that exploit this kind of access
Capture a single point-in-time snapshot of the project dashboard + metrics and append it to the partitioned JSONL file at ~/.ralph-hero/snapshots/<owner>/<projectNumber>.jsonl. Fetches all project items (full project scan, no silent 500-cap) so per-phase WIP and totals reflect every item regardless of board position. Append-only, schema-versioned. Returns the snapshot row that was written. It is categorised as a Write tool in the Ralph Hero MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__capture_snapshot: 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 Ralph Hero. Nothing to install.
ralph_hero__capture_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ralph_hero__capture_snapshot 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 ralph_hero__capture_snapshot. 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.
ralph_hero__capture_snapshot is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →