Retrieve detailed information about a specific Metabase database including connection details and schema - use this to examine database properties or troubleshoot connections
AI agents call get_database 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 and connection details about a database without modifying, executing, or deleting anything. It is fundamentally a Read operation. Severity is medium rather than low because connection details (passwords, hostnames, credentials) may be exposed if not properly redacted, which could aid attackers in lateral movement or unauthorized access.
From the tool's definition Tool name 'get_database' and description 'Retrieve detailed information about a specific Metabase database' clearly indicates a retrieval operation. The phrase 'examine database properties' confirms read-only intent.
Attacks that exploit this kind of access
Retrieve detailed information about a specific Metabase database including connection details and schema - use this to examine database properties or troubleshoot connections. 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: 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 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 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. 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 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 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 →