Get table lineage with parameter: full_name
AI agents call get_table_lineage to retrieve information from Databricks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays table lineage information from Databricks Unity Catalog without creating, modifying, deleting, or executing any operations. It is a read-only query operation that provides visibility into data dependencies. The blast radius of misuse is low—an agent could discover unwanted lineage relationships but cannot alter data or infrastructure.
From the tool's definition Tool name 'get_table_lineage' and description 'Get table lineage' indicate a retrieval/query operation with no modification or execution capability. The parameter 'full_name' is a simple identifier used to query lineage metadata.
Attacks that exploit this kind of access
Get table lineage with parameter: full_name. It is categorised as a Read tool in the Databricks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for get_table_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 Databricks MCP Server. Nothing to install.
get_table_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_table_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_table_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_table_lineage is provided by the Databricks MCP Server MCP server (robkisk/databricks-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 →