Get a card/question as a PNG image (base64 encoded).
AI agents call get_card_image to retrieve information from Metabase Mcp Navi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a visual representation (PNG image in base64 format) of an existing card/question in Metabase. It performs a read-only operation with no capacity to modify, delete, or execute arbitrary operations. The low severity reflects minimal blast radius—an agent misusing this tool could only retrieve dashboard visualizations it has access to, not alter data or trigger external actions.
From the tool's definition Tool name 'get_card_image' and description 'Get a card/question as a PNG image' indicate retrieval/query of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get a card/question as a PNG image (base64 encoded). It is categorised as a Read tool in the Metabase Mcp Navi MCP Server, which means it retrieves data without modifying state.
Register the Metabase Mcp Navi MCP server in PolicyLayer and add a rule for get_card_image: 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 Navi. Nothing to install.
get_card_image 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_card_image 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_card_image. 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_card_image is provided by the Metabase Mcp Navi MCP server (manish-coder-1007/metabase-mcp-navi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →