chronica_save_entry · Chronica MCP: Risk & Policy

WHAT IT DOES

What chronica_save_entry does on Chronica

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

WHY IT NEEDS A POLICY

Why chronica_save_entry needs a policy

This tool creates or modifies entries in a persistent memory store. It is reversible (entries can be deleted or modified later), placing it in the Write category rather than Destructive. Severity is medium because misuse could result in corruption or pollution of a user's memory store, but the impact is limited to a single user's session context and is not destructive or financial.

From the tool's definition Tool name 'chronica_save_entry' suggests creating or persisting data entries. The server is described as a 'Persistent memory MCP server' with 'auto-save' functionality. The tool name follows Write-category patterns (save, create, persist).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chronica_save_entry Rate-limited

chronica_save_entry 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": {
    "chronica_save_entry": {
      "limits": [
        {
          "counter": "chronica_save_entry_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 Chronica, so you can run agents against it safely.

FAQ

Questions about chronica_save_entry

What does the chronica_save_entry tool do? +

chronica_save_entry. It is categorised as a Write tool in the Chronica MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chronica_save_entry? +

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

What risk level is chronica_save_entry? +

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

Can I rate-limit chronica_save_entry? +

Yes. Add a rate_limit block to the chronica_save_entry 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 chronica_save_entry completely? +

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

chronica_save_entry is provided by the Chronica MCP server (nic9dev/chronica). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.