get_card

Get details of a specific question/card

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1luvc0d3-metabase-mcp/get-card.md

WHAT IT DOES

What get_card does on Metabase MCP

AI agents call get_card 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.

RISK

Why get_card is rated Low

This tool retrieves metadata and details about an existing Metabase card/question. It performs a read-only query operation with no capability to modify, delete, or execute data operations. The description explicitly indicates 'Get' (retrieval) semantics. No side effects are implied.

From the tool's definition Tool name 'get_card' and description 'Get details of a specific question/card' indicate retrieval of information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_card 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 get_card, this is the rule to start with:

get_card Allowed

get_card is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_card": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every get_card call is checked against it from then on.

FAQ

Questions about get_card

What does the get_card tool do? +

Get details of a specific question/card. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_card? +

Register the Metabase MCP server in PolicyLayer and add a rule for get_card: 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.

What risk level is get_card? +

get_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_card? +

Yes. Add a rate_limit block to the get_card 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.

How do I block get_card completely? +

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

get_card 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.

KEEP EXPLORING

More on Metabase, and thousands of servers like it.

This server

All 30 Metabase tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →