update_card_parameters · Metabase MCP: Risk & Policy

WHAT IT DOES

What update_card_parameters does on Metabase

AI agents use update_card_parameters 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_parameters needs a policy

The tool performs an update operation on card parameters, which is a reversible modification of data/configuration. This falls under Write category rather than Execute or Destructive because it changes settings rather than executing queries or permanently deleting resources. Severity is medium because misconfiguration could alter dashboard behavior or expose unintended data, but changes are reversible.

From the tool's definition Tool name 'update_card_parameters' indicates modification of card settings/parameters within Metabase. No description provided, but context of sibling tools (create_card, execute_card) and server function (dashboard management, analytics automation) suggests…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_card_parameters Rate-limited

update_card_parameters 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_parameters": {
      "limits": [
        {
          "counter": "update_card_parameters_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_parameters

What does the update_card_parameters tool do? +

update_card_parameters. 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_parameters? +

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

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

Can I rate-limit update_card_parameters? +

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

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

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