update_table · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_table does on Metabase MCP Server

AI agents use update_table 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_table needs a policy

The tool creates or modifies data and metadata reversibly (display name, description, field settings) without deleting or destroying data. This fits the Write category. Severity is medium because misconfiguration of table metadata could impact query results or user understanding of data, but changes are reversible.

From the tool's definition Tool name is 'update_table' with description stating it 'Update table configuration including display name, description, and field settings.' This modifies metadata and configuration of tables reversibly through customization and data model changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_table Rate-limited

update_table 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_table": {
      "limits": [
        {
          "counter": "update_table_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_table

What does the update_table tool do? +

Update table configuration including display name, description, and field settings - use this to customize presentation, update metadata, or configure data model. 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_table? +

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

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

Can I rate-limit update_table? +

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

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

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