update_database · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_database does on Metabase MCP Server

AI agents use update_database to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.

WHY IT NEEDS A POLICY

Why update_database needs a policy

This tool modifies database configuration and credentials, which are critical system settings. While changes are theoretically reversible (Write rather than Destructive), the high severity reflects the blast radius: compromised or incorrectly modified credentials could break data pipelines, expose sensitive connection information, or redirect queries to unauthorized databases.

From the tool's definition Tool description states it can "Update database configuration including name, connection details, and sync settings". The verb "update" combined with "connection details" and "credentials" indicates reversible modification of sensitive system configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_database Rate-limited

update_database stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_database": {
      "limits": [
        {
          "counter": "update_database_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_database

What does the update_database tool do? +

Update database configuration including name, connection details, and sync settings - use this to maintain connections, update credentials, or modify sync behavior. It is categorised as a Write tool in the Metabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_database? +

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

What risk level is update_database? +

update_database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_database? +

Yes. Add a rate_limit block to the update_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 update_database completely? +

Set action: deny in the PolicyLayer policy for update_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 update_database? +

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