update_card_visualization
Update visualization settings for a card
This record as markdown: /tools/zsh52013148087-metabase-mcp/update-card-visualization.md
What update_card_visualization does on Metabase Analytics Integration Server
AI agents use update_card_visualization to create or update resources in Metabase Analytics Integration Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase Analytics Integration Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
card_id | number | — | ID of the card to update |
viz_settings | object | — | New visualization settings |
Parameters from the server's own tool schema.
Why update_card_visualization is rated Medium
The tool modifies card visualization properties but does not delete the underlying card or data. Changes to visualization settings are reversible—they can be updated again or reverted to previous states. This places it squarely in the Write category.
From the tool's definition Tool updates visualization settings for a card in Metabase. The description indicates modification of existing card configuration ("Update visualization settings"), which is a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs update_card_visualization safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase Analytics Integration Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_card_visualization, this is the rule to start with:
update_card_visualization 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every update_card_visualization call is checked against it from then on.
Questions about update_card_visualization
Update visualization settings for a card. It is categorised as a Write tool in the Metabase Analytics Integration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_card_visualization accepts 2 parameters: card_id, viz_settings. The full parameter table on this page comes from the server's own tool schema.
Register the Metabase Analytics Integration Server MCP server in PolicyLayer and add a rule for update_card_visualization: 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 Analytics Integration Server. Nothing to install.
update_card_visualization is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_card_visualization 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.
Set action: deny in the PolicyLayer policy for update_card_visualization. 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.
update_card_visualization is provided by the Metabase Analytics Integration Server MCP server (zsh52013148087/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase Analytics Integration Server, and thousands of servers like it.
Across the catalogue