Get detailed information about a specific dashboard.
AI agents call get_dashboard to retrieve information from Metabase Mcp Navi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries dashboard information with no side effects. It does not create, modify, delete, or execute operations—it only fetches existing data. This is a classic Read operation. Severity is low because dashboard metadata disclosure has limited blast radius unless dashboards contain highly sensitive business intelligence, but the tool itself performs no dangerous action.
From the tool's definition Tool name 'get_dashboard' and description 'Get detailed information about a specific dashboard' indicate retrieval of dashboard metadata without modification or execution of queries.
Attacks that exploit this kind of access
Get detailed information about a specific dashboard. It is categorised as a Read tool in the Metabase Mcp Navi MCP Server, which means it retrieves data without modifying state.
Register the Metabase Mcp Navi MCP server in PolicyLayer and add a rule for get_dashboard: 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 Navi. Nothing to install.
get_dashboard 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 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. 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 is provided by the Metabase Mcp Navi MCP server (manish-coder-1007/metabase-mcp-navi). 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 →