save_dashboard_to_collection · Metabase MCP Server MCP

WHAT IT DOES

What save_dashboard_to_collection does on Metabase MCP Server

AI agents use save_dashboard_to_collection to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.

WHY IT NEEDS A POLICY

Why save_dashboard_to_collection needs a policy

This tool creates or modifies dashboard objects within collections, which is a reversible Write operation. It does not execute arbitrary queries, delete data irreversibly, or move financial resources. The medium severity reflects that unauthorized dashboard creation/modification could lead to data exposure or confusion in a shared analytics platform, but the action is reversible through deletion or modification.

From the tool's definition Tool name 'save_dashboard_to_collection' and description 'Save a dashboard object directly into a specific collection' indicate creation or modification of dashboard objects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_dashboard_to_collection Rate-limited

save_dashboard_to_collection stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_dashboard_to_collection": {
      "limits": [
        {
          "counter": "save_dashboard_to_collection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metabase MCP Server, so you can run agents against it safely.

FAQ

Questions about save_dashboard_to_collection

What does the save_dashboard_to_collection tool do? +

Save a dashboard object directly into a specific collection - use this for organized dashboard creation or bulk imports. It is categorised as a Write tool in the Metabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_dashboard_to_collection? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for save_dashboard_to_collection: 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.

What risk level is save_dashboard_to_collection? +

save_dashboard_to_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_dashboard_to_collection? +

Yes. Add a rate_limit block to the save_dashboard_to_collection 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.

How do I block save_dashboard_to_collection completely? +

Set action: deny in the PolicyLayer policy for save_dashboard_to_collection. 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.

What MCP server provides save_dashboard_to_collection? +

save_dashboard_to_collection 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.