list_cards
List questions/cards in Metabase. Returns up to 100 cards. Use search_content for discovery.
This record as markdown: /tools/1luvc0d3-metabase-mcp/list-cards.md
What list_cards does on Metabase MCP
AI agents call list_cards to retrieve information from Metabase MCP 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
This tool performs a simple query/list operation to retrieve card metadata from Metabase. It has no capability to modify, delete, execute, or affect data. The blast radius is minimal—at worst, an agent could learn about available cards in the system, which is low sensitivity information. Confidence is high due to the clear read-only nature of the operation.
From the tool's definition Tool description explicitly states 'List questions/cards in Metabase' and 'Returns up to 100 cards', which are read-only retrieval operations. No modifications, deletions, or side effects are mentioned.
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 MCP, 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 MCP, apply this rule, and every list_cards call is checked against it from then on.
Questions about list_cards
List questions/cards in Metabase. Returns up to 100 cards. Use search_content for discovery. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Metabase 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 MCP. 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 MCP server (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase, and thousands of servers like it.
This server
Across the catalogue