Trace the provenance chain of a document. Returns a tree { sources: [{filePath, ...}], derivatives: [{filePath, ...}] } showing which read documents informed this document (sources, traced upstream) and which created documents derived from it (derivatives, traced downstream). Lineage is recorded ...
AI agents call get-lineage to retrieve information from MCP Document Processor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get-lineage is a pure information retrieval operation that traces document provenance metadata. It queries and returns document relationship data (sources and derivatives) with no side effects, no data modification, and no code execution. This clearly falls under Read category (retrieve/query operations with no side effects).
From the tool's definition The tool 'Trace the provenance chain of a document. Returns a tree { sources: [{filePath, ...}], derivatives: [{filePath, ...}] }' — it retrieves and queries historical relationships between documents without modifying any data or executing operations.
Attacks that exploit this kind of access
Trace the provenance chain of a document. Returns a tree { sources: [{filePath, ...}], derivatives: [{filePath, ...}] } showing which read documents informed this document (sources, traced upstream) and which created documents derived from it (derivatives, traced downstream). Lineage is recorded automatically when read-doc and create-doc are called within the same session. It is categorised as a Read tool in the MCP Document Processor MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Processor MCP server in PolicyLayer and add a rule for get-lineage: 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 MCP Document Processor. Nothing to install.
get-lineage 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-lineage 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-lineage. 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-lineage is provided by the MCP Document Processor MCP server (leanzero-srl/leanzero-mcp-doc-processor). 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 →