📊 [SAFE] List all metrics (saved aggregations) in Metabase. Metrics are reusable calculations like
AI agents call list_metrics 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 enumerates existing metrics without creating, modifying, deleting, or executing any operations. It is a pure query operation that returns information about saved aggregations. The explicit '[SAFE]' marking in the description further confirms its non-destructive nature. No write, execute, destructive, or financial operations are involved.
From the tool's definition Tool name is 'list_metrics' and description states '[SAFE] List all metrics (saved aggregations) in Metabase.' The verb 'list' and the bracketed '[SAFE]' designation indicate a read-only retrieval operation with no side effects.
Attacks that exploit this kind of access
📊 [SAFE] List all metrics (saved aggregations) in Metabase. Metrics are reusable calculations like. 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_metrics: 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_metrics 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_metrics 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_metrics. 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_metrics is provided by the Metabase MCP Server MCP server (mikela92/metabase-mcp-mab). 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 →