Retrieve detailed information about a specific schema including tables and objects - use this to explore schema contents or understand organization
AI agents call get_database_schema 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 queries and returns schema metadata (tables, objects, organization) without modifying data or triggering external operations. It is a passive information retrieval operation typical of schema exploration, with no destructive, financial, or execution components.
From the tool's definition Tool name and description indicate retrieval of information: 'Retrieve detailed information about a specific schema including tables and objects' and 'use this to explore schema contents or understand organization'.
Attacks that exploit this kind of access
Retrieve detailed information about a specific schema including tables and objects - use this to explore schema contents or understand organization. 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 get_database_schema: 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.
get_database_schema 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_database_schema 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_database_schema. 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_database_schema 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.
get_database_schema is one line of Metabase MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →