add_event · Case Chronology MCP: Risk & Policy

WHAT IT DOES

What add_event does on Case Chronology

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

WHY IT NEEDS A POLICY

Why add_event needs a policy

This tool creates or modifies data in a reversible manner (new events can be added to a legal case timeline). While not destructive or financially sensitive, the ability to inject false or misleading events into a case chronology could cause significant harm in legal proceedings if misused by an AI agent, warranting medium severity.

From the tool's definition Tool name 'add_event' and description 'Add a chronology event' indicates creation of new data records in a chronological timeline system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_event Rate-limited

add_event 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": {
    "add_event": {
      "limits": [
        {
          "counter": "add_event_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 Case Chronology, so you can run agents against it safely.

FAQ

Questions about add_event

What does the add_event tool do? +

Add a chronology event with automatic date parsing. It is categorised as a Write tool in the Case Chronology MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_event? +

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

What risk level is add_event? +

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

Can I rate-limit add_event? +

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

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

add_event is provided by the Case Chronology MCP server (medelman17/case-chronology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.