Parse a document and extract potential chronology events
AI agents call parse_document 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 reads and analyzes a document to extract information (events) from it. It does not modify, delete, or create any data — it only parses and returns extracted event candidates. The word 'extract' and 'potential' suggest it is a read/query operation with no side effects. Severity is low since misuse would at most expose document contents.
From the tool's definition Parse a document and extract potential chronology events
Attacks that exploit this kind of access
Parse a document and extract potential chronology events. 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 parse_document: 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.
parse_document 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 parse_document 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 parse_document. 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.
parse_document 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 →