This record as markdown: /tools/1luvc0d3-metabase-mcp/list-dashboards.md
What list_dashboards does on Metabase MCP
AI agents call list_dashboards 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.
Why list_dashboards is rated Low
This tool retrieves and lists existing dashboards without creating, modifying, deleting, or executing any operations. It is a read-only query operation with minimal security risk—the blast radius is limited to information disclosure of dashboard metadata that likely has appropriate access controls within Metabase.
From the tool's definition Tool name 'list_dashboards' and description 'List all dashboards in Metabase' indicate a query/retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs list_dashboards 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 list_dashboards, this is the rule to start with:
list_dashboards is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every list_dashboards call is checked against it from then on.
Questions about list_dashboards
List all dashboards in Metabase. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Metabase 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. 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 (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase, and thousands of servers like it.
This server
Across the catalogue