update_card_display · Metabase MCP: Risk & Policy

WHAT IT DOES

What update_card_display does on Metabase

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

WHY IT NEEDS A POLICY

Why update_card_display needs a policy

The 'update_' prefix combined with 'card_display' (a component that can be modified reversibly) places this in Write category. The tool modifies existing dashboard/analytics objects rather than deleting them or executing arbitrary operations. However, confidence is moderate (0.7) because the description is empty, preventing full assessment of scope and side effects.

From the tool's definition Tool name 'update_card_display' indicates modification of a card's display properties in Metabase. Context shows cards are analytics/visualization objects created and managed within Metabase dashboards.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_card_display Rate-limited

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

FAQ

Questions about update_card_display

What does the update_card_display tool do? +

update_card_display. It is categorised as a Write tool in the Metabase 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_card_display? +

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

What risk level is update_card_display? +

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

Can I rate-limit update_card_display? +

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

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

update_card_display is provided by the Metabase MCP server (voducdan/matebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.