list_tables
List all tables in a database
This record as markdown: /tools/zsh52013148087-metabase-mcp/list-tables.md
What list_tables does on Metabase Analytics Integration Server
AI agents call list_tables 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 |
|---|---|---|---|
database_id | number | — | ID of the database |
include_cards | boolean | — | Whether to include saved questions/cards in the response |
include_tables | boolean | — | Whether to include tables in the response |
Parameters from the server's own tool schema.
Why list_tables is rated Low
This is a straightforward metadata retrieval operation with no side effects. It queries structural information about the database schema. The action is read-only, presenting minimal risk even in adversarial scenarios, as listing tables does not expose data contents, execute code, or alter state.
From the tool's definition Tool name is 'list_tables' and description states 'List all tables in a database' — this retrieves metadata about available tables without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs list_tables 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 list_tables, this is the rule to start with:
list_tables 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 list_tables call is checked against it from then on.
Questions about list_tables
List all tables in a database. It is categorised as a Read tool in the Metabase Analytics Integration Server MCP Server, which means it retrieves data without modifying state.
list_tables accepts 3 parameters: database_id, include_cards, include_tables. 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 list_tables: 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.
list_tables 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 list_tables 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 list_tables. 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.
list_tables 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