Export chronology in various formats
AI agents call export_chronology to retrieve information from Case Chronology without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting a chronology reads/retrieves existing timeline data and converts it to a different format for output. This is a read operation with no side effects — it does not create, modify, delete, or trigger external operations. The description mentions 'export' and 'various formats', consistent with data retrieval/serialization. Severity is low as misuse would only expose case timeline data.
From the tool's definition Export chronology in various formats
Attacks that exploit this kind of access
Export chronology in various formats. It is categorised as a Read tool in the Case Chronology MCP Server, which means it retrieves data without modifying state.
Register the Case Chronology MCP server in PolicyLayer and add a rule for export_chronology: 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.
export_chronology is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_chronology 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.
Set action: deny in the PolicyLayer policy for export_chronology. 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.
export_chronology 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →