get_table_related

Find tables and entities related through relationships or schemas - use this to discover connected data, find related content, or understand context

Server Metabase MCP Server thangnm93/metabase-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_table_related does on Metabase MCP Server

AI agents call get_table_related to retrieve information from Metabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_table_related needs a policy

This tool retrieves and queries relational metadata to help users discover connected data and understand schema relationships. It has no side effects, does not execute arbitrary code, and does not modify, delete, or move any data. The blast radius of misuse is minimal—an AI agent could at worst retrieve information about table relationships it shouldn't access, but cannot alter or destroy data.

From the tool's definition Tool name 'get_table_related' and description emphasize discovery and understanding: 'Find tables and entities related through relationships or schemas - use this to discover connected data, find related content, or understand context'.

Questions about get_table_related

What does the get_table_related tool do? +

Find tables and entities related through relationships or schemas - use this to discover connected data, find related content, or understand context. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_table_related? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for get_table_related: 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 Metabase MCP Server. Nothing to install.

What risk level is get_table_related? +

get_table_related is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_table_related? +

Yes. Add a rate_limit block to the get_table_related 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.

How do I block get_table_related completely? +

Set action: deny in the PolicyLayer policy for get_table_related. 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.

What MCP server provides get_table_related? +

get_table_related is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.