Get full details for a specific dashboard, including its dashcards and parameters.
AI agents call get_dashboard_details 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 retrieves and displays dashboard metadata and configuration. It performs a query operation that does not modify, delete, or execute any data or code. The action is non-destructive information retrieval, fitting the Read category (low severity) as misuse would only expose existing dashboard information rather than cause operational impact.
From the tool's definition Tool description states 'Get full details for a specific dashboard, including its dashcards and parameters' — explicitly a retrieval operation with no modification or execution implied. No side effects mentioned.
Attacks that exploit this kind of access
Get full details for a specific dashboard, including its dashcards and parameters. 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_details: 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_details 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_details 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_details. 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_details is provided by the Metabase MCP Server MCP server (traghav/metabase-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 →