get_table_fields
Get all fields/columns in a table
This record as markdown: /tools/zsh52013148087-metabase-mcp/get-table-fields.md
What get_table_fields does on Metabase Analytics Integration Server
AI agents call get_table_fields to retrieve information from Metabase Analytics Integration Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
table_id | number | — | ID of the table |
Parameters from the server's own tool schema.
Why get_table_fields is rated Low
This tool retrieves structural information about a database table (field names and types) without executing queries, modifying data, or triggering side effects. It is a read-only schema discovery operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_table_fields' and description 'Get all fields/columns in a table' indicate retrieval of schema metadata with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_table_fields safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase Analytics Integration Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_table_fields, this is the rule to start with:
get_table_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every get_table_fields call is checked against it from then on.
Questions about get_table_fields
Get all fields/columns in a table. It is categorised as a Read tool in the Metabase Analytics Integration Server MCP Server, which means it retrieves data without modifying state.
get_table_fields accepts 1 parameter: table_id. The full parameter table on this page comes from the server's own tool schema.
Register the Metabase Analytics Integration Server MCP server in PolicyLayer and add a rule for get_table_fields: 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 Analytics Integration Server. Nothing to install.
get_table_fields 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_fields 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_fields. 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_fields is provided by the Metabase Analytics Integration Server MCP server (zsh52013148087/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase Analytics Integration Server, and thousands of servers like it.
Across the catalogue