// SCAN REPORT

Chronos MCP

12 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

5 can modify or destroy data

7 read-only

12 tools total

Community server · catalogue entry verified 03/07/2026

How to control Chronos MCP ↓

TOOL MAP

What Chronos MCP exposes to your agents

Read (7) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Chronos MCP tools

Destructive · High forget On a server designed for persistent local memory and knowledge graph management, a tool named 'forget' most likely removes or purges stored memories, notes, or knowledge graph nodes — an irreversible deletion operation. Write · Medium add_constraint The tool name 'add_constraint' indicates creation or modification of constraint data within the knowledge graph system. Write · Medium add_event The 'add_event' tool appears to create or append entries to a time-series knowledge graph. Write · Medium update_memory The tool creates or modifies data reversibly within a local knowledge graph.

5 of Chronos MCP's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Chronos MCP

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

Deny destructive operations

{
  "forget": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_constraint": {
    "limits": [
      {
        "counter": "add_constraint_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_causal": {
    "limits": [
      {
        "counter": "analyze_causal_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 Chronos MCP — 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 CHRONOS →

Instant setup, no code required.

FULL CATALOGUE

All 12 Chronos MCP tools

DESTRUCTIVE 1 tools

Destructive forget forget

WRITE 4 tools

Write add_constraint add_constraint Write add_event add_event Write remember remember Write update_memory update_memory

READ 7 tools

Read analyze_causal analyze_causal Read analyze_structure analyze_structure Read query_at query_at Read query_similar query_similar Read query_similar_memories query_similar_memories Read recall recall Read suggest_next_tasks suggest_next_tasks

FAQ

Questions about Chronos MCP

Can an AI agent delete data through the Chronos MCP server? +

Yes. The Chronos MCP server exposes 1 destructive tools including forget. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Chronos MCP? +

The Chronos MCP server has 4 write tools including add_constraint, add_event, remember. 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 Chronos MCP.

How many tools does the Chronos MCP server expose? +

12 tools across 2 categories: Read, Write. 7 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Chronos MCP? +

Register the Chronos 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 Chronos MCP tool call.

Deterministic rules across all 12 Chronos MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CHRONOS →

Instant setup, no code required.

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