add_card_to_dashboard

// WHEN AI AGENTS USE THIS TOOL

AI agents use add_card_to_dashboard to create or modify resources in Metabase Analytics Integration Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON ADD_CARD_TO_DASHBOARD

Without a policy, an AI agent could call add_card_to_dashboard repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Metabase Analytics Integration Server.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

ryanmaule-metabase-mcp.yaml

tools:
  add_card_to_dashboard:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Metabase Analytics Integration Server policy for all 16 tools.

// DETAILS

Tool Name add_card_to_dashboard

Category Write

MCP Server Metabase Analytics Integration Server MCP Server

Risk Level Medium

// MORE METABASE ANALYTICS INTEGRATION SERVER TOOLS

Destructive delete_dashboard Execute execute_card Execute execute_query Write create_card Write create_collection Write create_dashboard Write update_card_visualization Write update_dashboard

View all 16 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like add_card_to_dashboard have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the add_card_to_dashboard tool do? +

Add a card to a dashboard. 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.

How do I enforce a policy on add_card_to_dashboard? +

Add a rule in your Intercept YAML policy under the tools section for add_card_to_dashboard. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Metabase Analytics Integration Server MCP server.

What risk level is add_card_to_dashboard? +

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

Can I rate-limit add_card_to_dashboard? +

Yes. Add a rate_limit block to the add_card_to_dashboard rule in your Intercept 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 add_card_to_dashboard completely? +

Set action: deny in the Intercept policy for add_card_to_dashboard. 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 add_card_to_dashboard? +

add_card_to_dashboard is provided by the Metabase Analytics Integration Server MCP server (ryanmaule/metabase-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

add_card_to_dashboard

Enforce policies on Metabase Analytics Integration Server