get_database_metadata

THE RISK

Low Risk

Why get_database_metadata needs a policy

The tool retrieves database metadata (structure, schema information) without creating, modifying, deleting, or executing any operations. This is a standard read operation. The context of sibling tools (execute_action, run_database_query) confirms this is informational only.

From the tool's definition Tool description states 'Get detailed metadata for a specific database' with no mention of modification, deletion, or execution of code. Metadata retrieval is a read-only operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_database_metadata gives an agent:

POLICY

How to control get_database_metadata

PolicyLayer is an MCP gateway — it sits between your AI agents and Metabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_database_metadata:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_database_metadata": {}
  }
}

get_database_metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Metabase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Metabase MCP Server tools

Execute execute_action Execute a Metabase action with parameters Execute run_database_query Execute a SQL query against a database Read db_overview Get a high-level overview of all tables in a database Read get_action_details Get detailed information about a specific action Read list_actions List all actions configured in Metabase Read list_databases List all databases configured in Metabase Read table_detail Get detailed information about a specific table Read visualize_database_relationships Generate a visual representation of database relationships

All 9 Metabase MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_database_metadata

What does the get_database_metadata tool do? +

Get detailed metadata for a specific database. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_database_metadata? +

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.

What risk level is get_database_metadata? +

get_database_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_database_metadata? +

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.

How do I block get_database_metadata completely? +

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.

What MCP server provides get_database_metadata? +

get_database_metadata is provided by the Metabase MCP Server MCP server (sazboxai/mcp_metabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Metabase MCP Server tool call.

Start from Metabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →