Retrieve comprehensive database metadata including tables, fields, and relationships - use this to understand structure or build dynamic queries
AI agents call get_database_metadata 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 only queries and returns metadata about database structure (tables, fields, relationships). It has no side effects, cannot modify or delete data, and does not execute arbitrary operations. It falls squarely into the Read category. Severity is low because metadata disclosure, while potentially informative to an attacker, does not directly compromise data or systems without further action.
From the tool's definition Tool name 'get_database_metadata' and description 'Retrieve comprehensive database metadata including tables, fields, and relationships' indicate pure retrieval with no modification.
Attacks that exploit this kind of access
Retrieve comprehensive database metadata including tables, fields, and relationships - use this to understand structure or build dynamic queries. 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_metadata: 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_metadata 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_metadata 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_metadata. 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_metadata 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.
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 →