Search dashboards by name or description text - use this to find specific dashboards or discover related analytical content
AI agents call search_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 search query to discover and retrieve dashboards without creating, modifying, deleting, or executing any operations. It has no side effects and cannot alter data or trigger external actions. The blast radius of misuse is minimal—an attacker could discover dashboards but cannot access their contents, modify them, or extract sensitive data beyond knowing dashboard names exist.
From the tool's definition Tool description states 'Search dashboards by name or description text' which is a query/search operation with no modification or execution capability. The verb 'search' and 'find' indicate read-only retrieval.
Attacks that exploit this kind of access
Search dashboards by name or description text - use this to find specific dashboards or discover related analytical content. 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 search_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.
search_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 search_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 search_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.
search_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 →