get_dashboard_cards
Get all cards in a dashboard
This record as markdown: /tools/zsh52013148087-metabase-mcp/get-dashboard-cards.md
What get_dashboard_cards does on Metabase Analytics Integration Server
AI agents call get_dashboard_cards to retrieve information from Metabase Analytics Integration Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dashboard_id | number | — | ID of the dashboard |
Parameters from the server's own tool schema.
Why get_dashboard_cards is rated Low
This tool retrieves and queries dashboard card metadata with no side effects. It falls clearly into the Read category as a data retrieval operation. Severity is low because access to dashboard metadata poses minimal risk unless the dashboard contains highly sensitive analytics, but the tool itself cannot modify or execute anything dangerous.
From the tool's definition Tool name 'get_dashboard_cards' and description 'Get all cards in a dashboard' indicate data retrieval without modification. The verb 'Get' and absence of language indicating side effects (create, delete, modify, execute) confirm read-only behavior.
Attacks that exploit this kind of access
The rule that runs get_dashboard_cards 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 get_dashboard_cards, this is the rule to start with:
get_dashboard_cards is read-only, so it stays allowed. 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 get_dashboard_cards call is checked against it from then on.
Questions about get_dashboard_cards
Get all cards in a dashboard. It is categorised as a Read tool in the Metabase Analytics Integration Server MCP Server, which means it retrieves data without modifying state.
get_dashboard_cards accepts 1 parameter: dashboard_id. 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 get_dashboard_cards: 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.
get_dashboard_cards is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_dashboard_cards 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 get_dashboard_cards. 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.
get_dashboard_cards 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