Retrieve all Metabase dashboards - use this to discover available dashboards, get an overview of analytical content, or find specific dashboards
AI agents call list_dashboards 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 a query/retrieval operation on existing dashboards without creating, modifying, deleting, or executing any actions. It has no side effects beyond returning data. The blast radius of misuse is minimal—an AI agent could at worst enumerate dashboards, but cannot alter them or access sensitive data beyond what Metabase's permissions already expose. Classification: Read with low severity.
From the tool's definition The tool name is 'list_dashboards' and the description states 'Retrieve all Metabase dashboards' and emphasizes discovery and overview purposes with no modification or execution capabilities.
Attacks that exploit this kind of access
Retrieve all Metabase dashboards - use this to discover available dashboards, get an overview of analytical content, or find specific dashboards. 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 list_dashboards: 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.
list_dashboards 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_dashboards 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_dashboards. 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_dashboards 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 →