list_cards
List all questions/cards in Metabase
This record as markdown: /tools/zsh52013148087-metabase-mcp/list-cards.md
What list_cards does on Metabase Analytics Integration Server
AI agents call list_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.
Why list_cards is rated Low
The tool performs a read-only operation that retrieves a list of existing questions/cards from Metabase. There are no destructive, write, execute, or financial implications. The blast radius of misuse is minimal—an AI agent listing cards cannot cause harm beyond potentially accessing information visibility. This is a standard Read category tool.
From the tool's definition Tool name 'list_cards' and description 'List all questions/cards in Metabase' indicate a retrieval/query operation with no side effects. This is a listing operation that retrieves existing data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs list_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 list_cards, this is the rule to start with:
list_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 list_cards call is checked against it from then on.
Questions about list_cards
List all questions/cards in Metabase. It is categorised as a Read tool in the Metabase Analytics Integration Server MCP Server, which means it retrieves data without modifying state.
Register the Metabase Analytics Integration Server MCP server in PolicyLayer and add a rule for list_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.
list_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 list_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 list_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.
list_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