update_event · Case Chronology MCP: Risk & Policy

WHAT IT DOES

What update_event does on Case Chronology

AI agents use update_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 update_event needs a policy

This tool creates or modifies data reversibly by updating existing events in a legal case timeline. While it changes state, the modification is not permanent or irreversible (data can be corrected later), placing it in the Write category. Severity is medium because misuse could alter important legal case records, but the reversible nature and lack of data destruction prevents it from being high or critical.

From the tool's definition Tool is described as 'Update an existing chronology event' which modifies data within the chronology system. The action is reversible through subsequent updates or corrections, distinguishing it from destructive deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_event Rate-limited

update_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": {
    "update_event": {
      "limits": [
        {
          "counter": "update_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 update_event

What does the update_event tool do? +

Update an existing chronology event. 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 update_event? +

Register the Case Chronology MCP server in PolicyLayer and add a rule for update_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 update_event? +

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

Can I rate-limit update_event? +

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

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

update_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.