Execute a Metabase card and export the results in a specific format (CSV, Excel, JSON, etc.) - use this to download data for external analysis, create reports for stakeholders, or integrate query results with other systems
AI agents use export_card_result to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.
An AI agent can call export_card_result faster than any human can review — one bad instruction and it creates or modifies resources in Metabase MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Execute a Metabase card and export the results in a specific format (CSV, Excel, JSON, etc.) - use this to download data for external analysis, create reports for stakeholders, or integrate query results with other systems. It is categorised as a Write tool in the Metabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for export_card_result: 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 Server. Nothing to install.
export_card_result is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_card_result 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 export_card_result. 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.
export_card_result is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). 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 →