get_lineage_paths_between
AI agents call get_lineage_paths_between to retrieve information from DataHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve and display data lineage information between entities—showing relationships and dependencies without modifying, deleting, or executing operations. It follows the 'get_' prefix convention used for read operations in this MCP server. The low severity reflects that lineage data retrieval has no side effects or blast radius on actual data systems.
From the tool's definition Tool name 'get_lineage_paths_between' indicates a retrieval operation consistent with the server's stated capability to 'explore data lineage'.
Attacks that exploit this kind of access
get_lineage_paths_between. It is categorised as a Read tool in the DataHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataHub MCP Server MCP server in PolicyLayer and add a rule for get_lineage_paths_between: 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 DataHub MCP Server. Nothing to install.
get_lineage_paths_between 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_paths_between 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_paths_between. 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_paths_between is provided by the DataHub MCP Server MCP server (shemreader/mcp-server-datahub). 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 →