Get the dependency graph of fields in a table. Analyzes formula fields, lookup fields, rollup fields, and link fields, and returns recursive upstream/downstream dependencies and a Mermaid visualization.
AI agents call get_field_dependency_graph to retrieve information from Teable MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the structure and relationships of fields within a table to provide dependency analysis and visualization. It performs no mutations, deletions, or side effects—only retrieval and analysis of existing metadata.
From the tool's definition The tool 'get_field_dependency_graph' retrieves and analyzes dependency information about fields in a table, returning visualization data.
Documented attack patterns abuse exactly the kind of access get_field_dependency_graph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teable MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_field_dependency_graph:
{
"version": "1",
"default": "deny",
"tools": {
"get_field_dependency_graph": {}
}
}get_field_dependency_graph is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the dependency graph of fields in a table. Analyzes formula fields, lookup fields, rollup fields, and link fields, and returns recursive upstream/downstream dependencies and a Mermaid visualization. It is categorised as a Read tool in the Teable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Teable MCP Server MCP server in PolicyLayer and add a rule for get_field_dependency_graph: 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 Teable MCP Server. Nothing to install.
get_field_dependency_graph 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_field_dependency_graph 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_field_dependency_graph. 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_field_dependency_graph is provided by the Teable MCP Server MCP server (ltphat2204/teable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teable MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Teable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.