compare_metrics

What compare_metrics does on Metabase MCP

AI agents call compare_metrics 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 compare_metrics is rated Low

The tool retrieves and compares existing metric data without creating, modifying, deleting, or executing external operations. It is a query/analysis operation that has no side effects on the data or system state. Even in the context of Metabase dashboards and cards, comparison operations are fundamentally Read category—they examine and present data without changing it.

From the tool's definition Tool name 'compare_metrics' and description 'Compare two metrics or time periods' indicate data retrieval and analysis operations without modification or deletion. Comparison is a read-only analytical operation.

The rule that runs compare_metrics 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 compare_metrics, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_metrics": {}
  }
}

Questions about compare_metrics