sync_database_schema · Metabase MCP Server MCP

WHAT IT DOES

What sync_database_schema does on Metabase MCP Server

AI agents invoke sync_database_schema to trigger actions in Metabase MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why sync_database_schema needs a policy

This tool triggers an external operation (schema synchronization) on the Metabase platform. It does not merely read data, nor does it delete or modify data directly — it initiates a sync process that causes Metabase to re-scan the database and update its internal metadata cache.

From the tool's definition Initiate schema sync to update Metabase metadata cache

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_database_schema Rate-limited

sync_database_schema stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_database_schema": {
      "limits": [
        {
          "counter": "sync_database_schema_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metabase MCP Server, so you can run agents against it safely.

FAQ

Questions about sync_database_schema

What does the sync_database_schema tool do? +

Initiate schema sync to update Metabase metadata cache - use this after database changes to recognize new tables, columns, or relationships. It is categorised as a Execute tool in the Metabase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sync_database_schema? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for sync_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.

What risk level is sync_database_schema? +

sync_database_schema is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sync_database_schema? +

Yes. Add a rate_limit block to the sync_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.

How do I block sync_database_schema completely? +

Set action: deny in the PolicyLayer policy for sync_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.

What MCP server provides sync_database_schema? +

sync_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.