Get summary statistics about the chronology
AI agents call get_timeline_summary 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.
This tool retrieves and summarizes existing chronology data without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal blast radius—worst case, an AI agent could access summary statistics about case timelines, which is informational only.
From the tool's definition Tool name 'get_timeline_summary' and description 'Get summary statistics about the chronology' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get summary statistics about the chronology. 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 get_timeline_summary: 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.
get_timeline_summary 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 get_timeline_summary 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 get_timeline_summary. 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.
get_timeline_summary 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 →