# gns_roll_epoch

Roll all pending breadcrumbs into a new sealed epoch with a Merkle root. Returns { epoch_index, merkle_root, block_count, epoch_hash }. Call this at the end of a session to produce a tamper-evident compliance snapshot.

Agent View of the PolicyLayer registry record for `gns_roll_epoch`. HTML page: https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-roll-epoch

## Facts

- Tool: `gns_roll_epoch`
- Server: Mcp Agentcore (`https://packagesmcp-perception-production.up.railway.app/mcp`) — https://policylayer.com/tools/com-geiant-mcp-agentcore.md
- Homepage: https://github.com/GNS-Foundation/geiant
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- 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": "gns_roll_epoch",
    "arguments": {}
  }
}
```

## Why gns_roll_epoch is rated Medium

This tool aggregates and seals pending audit/compliance records into a new immutable epoch with a Merkle root hash. It creates a new data structure (a sealed epoch) from existing pending breadcrumbs — this is a Write operation as it commits and creates a new record.

From the tool's own definition: "'Roll all pending breadcrumbs into a new sealed epoch with a Merkle root' and 'produce a tamper-evident compliance snapshot'"

Risk signals: Admin/system-level operation

## Use case

AI agents use gns_roll_epoch to create or update resources in Mcp Agentcore, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Agentcore environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Agentcore:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gns_roll_epoch": {
      "limits": [
        {
          "counter": "gns_roll_epoch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Agentcore (7)

- `perception_classify` — Execute — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-classify.md
- `perception_embed` — Other — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-embed.md
- `gns_get_compliance_report` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-compliance-report.md
- `gns_get_trust_score` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-get-trust-score.md
- `gns_verify_chain` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/gns-verify-chain.md
- `perception_fetch_tile` — Read — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-fetch-tile.md
- `perception_weather` — Write — https://policylayer.com/tools/com-geiant-mcp-agentcore/perception-weather.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=com-geiant-mcp-agentcore · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geiant-mcp-agentcore