// SCAN REPORT

Chronica

10 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

2 can modify or destroy data

8 read-only

10 tools total

Community server · catalogue entry verified 03/07/2026

How to control Chronica ↓

TOOL MAP

What Chronica exposes to your agents

Read (8) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Chronica tools

Write · Low chronica_create_thread Creating a thread is a reversible write operation—threads can be modified, deleted, or abandoned without permanent harm. Write · Medium chronica_save_entry This tool creates or modifies entries in a persistent memory store.

2 of Chronica's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Chronica

PolicyLayer is an MCP gateway — it sits between your AI agents and Chronica, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "chronica_create_thread": {
    "limits": [
      {
        "counter": "chronica_create_thread_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "chronica_compose_opening": {
    "limits": [
      {
        "counter": "chronica_compose_opening_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Chronica — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CHRONICA →

Instant setup, no code required.

FULL CATALOGUE

All 10 Chronica tools

WRITE 2 tools

Write chronica_create_thread 新しいスレッドを作成します。 Write chronica_save_entry chronica_save_entry

READ 8 tools

Read chronica_compose_opening chronica_compose_opening Read chronica_get_last_seen 指定されたスレッドタイプで最後に見た時刻を取得します。 Read chronica_get_thread_info 指定されたスレッドの情報を取得します。 Read chronica_list_threads chronica_list_threads Read chronica_search chronica_search Read chronica_session_tick chronica_session_tick Read chronica_summarize サマリーパックを生成します（Summary Pack v0.1.2）。 Read chronica_timeline chronica_timeline

FAQ

Questions about Chronica

How do I prevent bulk modifications through Chronica? +

The Chronica server has 2 write tools including chronica_create_thread, chronica_save_entry. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Chronica.

How many tools does the Chronica MCP server expose? +

10 tools across 2 categories: Read, Write. 8 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Chronica? +

Register the Chronica MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Chronica tool call.

Deterministic rules across all 10 Chronica tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CHRONICA →

Instant setup, no code required.

10 Chronica tools catalogued and risk-classified — across an index of 43,000+ MCP servers.