# get_dashboard_cards

Get all cards in a dashboard

Agent View of the PolicyLayer registry record for `get_dashboard_cards`. HTML page: https://policylayer.com/tools/zsh52013148087-metabase-mcp/get-dashboard-cards

## Facts

- Tool: `get_dashboard_cards`
- Server: Metabase Analytics Integration Server (`zsh52013148087/metabase-mcp`) — https://policylayer.com/tools/zsh52013148087-metabase-mcp.md
- Homepage: https://github.com/zsh52013148087/metabase-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `dashboard_id` | number | no | ID of the dashboard |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_dashboard_cards",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Metabase Analytics Integration Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_dashboard_cards": {}
  }
}
```

## Other tools on Metabase Analytics Integration Server (15)

- `delete_dashboard` — Destructive — https://policylayer.com/tools/zsh52013148087-metabase-mcp/delete-dashboard.md
- `execute_card` — Execute — https://policylayer.com/tools/zsh52013148087-metabase-mcp/execute-card.md
- `execute_query` — Execute — https://policylayer.com/tools/zsh52013148087-metabase-mcp/execute-query.md
- `get_table_fields` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/get-table-fields.md
- `list_cards` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-cards.md
- `list_collections` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-collections.md
- `list_dashboards` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-dashboards.md
- `list_databases` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-databases.md
- `list_tables` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-tables.md
- `add_card_to_dashboard` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/add-card-to-dashboard.md
- `create_card` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-card.md
- `create_collection` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-collection.md
- `create_dashboard` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-dashboard.md
- `update_card_visualization` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/update-card-visualization.md
- `update_dashboard` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/update-dashboard.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=zsh52013148087-metabase-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/zsh52013148087-metabase-mcp