Extract all queries from a dashboard with IDs resolved to actual table/column names - use this to understand dashboard data sources, audit queries, or plan migrations
AI agents call get_dashboard_queries to retrieve information from Metabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs query retrieval and analysis without creating, modifying, or deleting any data. It supports legitimate auditing and information-gathering activities. The blast radius of misuse is minimal—an AI agent could only extract information about existing queries, not alter infrastructure or data.
From the tool's definition Tool extracts and retrieves queries from a dashboard, resolving IDs to table/column names. The verb 'extract' and 'understand' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Extract all queries from a dashboard with IDs resolved to actual table/column names - use this to understand dashboard data sources, audit queries, or plan migrations. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for get_dashboard_queries: 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.
get_dashboard_queries 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_dashboard_queries 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_dashboard_queries. 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_dashboard_queries 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 →