📑 [SAFE] List all tables in a specific database. Use this to see what tables are available before querying. Risk: None - read-only operation.
AI agents call list_database_tables 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.
This tool retrieves metadata about available tables in a database without executing queries, modifying data, or triggering side effects. It is a read-only discovery operation, making it the lowest risk category. The explicit '[SAFE]' and 'read-only' labels in the description reinforce this classification.
From the tool's definition Tool description explicitly states '[SAFE] List all tables in a specific database' and 'read-only operation'. The tool name 'list_database_tables' indicates a retrieval/enumeration action with no modification or deletion capability.
Attacks that exploit this kind of access
📑 [SAFE] List all tables in a specific database. Use this to see what tables are available before querying. Risk: None - read-only operation. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for list_database_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 MCP Server. Nothing to install.
list_database_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_database_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_database_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_database_tables is provided by the Metabase MCP Server MCP server (mikela92/metabase-mcp-mab). 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 →