save_handoff_receipt · Chronicle MCP: Risk & Policy

WHAT IT DOES

What save_handoff_receipt does on Chronicle MCP

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

WHY IT NEEDS A POLICY

Why save_handoff_receipt needs a policy

This tool creates or modifies handoff receipt records within the Chronicle memory system. It is a Write operation because it persists new or updated handoff state data rather than retrieving it (Read), executing arbitrary code (Execute), or deleting data (Destructive).

From the tool's definition Tool name 'save_handoff_receipt' and description 'Save a structured, continuation-biased handoff receipt' indicate creation/modification of handoff state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_handoff_receipt Rate-limited

save_handoff_receipt stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_handoff_receipt": {
      "limits": [
        {
          "counter": "save_handoff_receipt_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chronicle MCP, so you can run agents against it safely.

FAQ

Questions about save_handoff_receipt

What does the save_handoff_receipt tool do? +

Save a structured, continuation-biased handoff receipt conforming to the strict state-machine DAG model. It is categorised as a Write tool in the Chronicle MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_handoff_receipt? +

Register the Chronicle MCP server in PolicyLayer and add a rule for save_handoff_receipt: 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 Chronicle MCP. Nothing to install.

What risk level is save_handoff_receipt? +

save_handoff_receipt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_handoff_receipt? +

Yes. Add a rate_limit block to the save_handoff_receipt 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.

How do I block save_handoff_receipt completely? +

Set action: deny in the PolicyLayer policy for save_handoff_receipt. 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.

What MCP server provides save_handoff_receipt? +

save_handoff_receipt is provided by the Chronicle MCP server (pypi:chronicle-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.