update_tables · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_tables does on Metabase MCP Server

AI agents use update_tables 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_tables needs a policy

The tool modifies table configuration and metadata in bulk across multiple tables. While updates are typically reversible (unlike destructive deletes), the bulk nature and potential to affect multiple tables' properties simultaneously creates significant blast radius if an AI agent applies incorrect settings across the system.

From the tool's definition Tool description states 'Bulk update multiple Metabase tables with same configuration' and 'update metadata, or modify table properties' - these are reversible modification operations affecting multiple tables.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tables Rate-limited

update_tables 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_tables": {
      "limits": [
        {
          "counter": "update_tables_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_tables

What does the update_tables tool do? +

Bulk update multiple Metabase tables with same configuration - use this to apply consistent settings, update metadata, or modify table properties efficiently. 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_tables? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for update_tables: 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_tables? +

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

Can I rate-limit update_tables? +

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

Set action: deny in the PolicyLayer policy for update_tables. 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_tables? +

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