sync_database · Metabase Mcp Navi MCP: Risk & Policy

WHAT IT DOES

What sync_database does on Metabase Mcp Navi

AI agents invoke sync_database to trigger actions in Metabase Mcp Navi. 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 needs a policy

This tool triggers an external operation (database metadata sync) rather than simply reading or writing data within Metabase. While not destructive in the sense of deletion, it executes a command that can affect system state, refresh rates, and potentially impact other users' views of the database.

From the tool's definition Tool name: 'sync_database'. Description: 'Trigger a sync of a database's metadata.' The verb 'Trigger' and 'sync' indicate initiation of an external operation (database metadata synchronization) whose effects depend on database state and are not immediately…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_database Rate-limited

sync_database 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": {
      "limits": [
        {
          "counter": "sync_database_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 Navi, so you can run agents against it safely.

FAQ

Questions about sync_database

What does the sync_database tool do? +

Trigger a sync of a database's metadata. It is categorised as a Execute tool in the Metabase Mcp Navi 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? +

Register the Metabase Mcp Navi MCP server in PolicyLayer and add a rule for sync_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 Navi. Nothing to install.

What risk level is sync_database? +

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

Can I rate-limit sync_database? +

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

How do I block sync_database completely? +

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

What MCP server provides sync_database? +

sync_database is provided by the Metabase Mcp Navi MCP server (manish-coder-1007/metabase-mcp-navi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.