list_collections

List all collections in Metabase

SERVERMetabase Analytics Integration Server SOURCEzsh52013148087/metabase-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/zsh52013148087-metabase-mcp/list-collections.md

WHAT IT DOES

What list_collections does on Metabase Analytics Integration Server

AI agents call list_collections to retrieve information from Metabase Analytics Integration Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_collections is rated Low

This tool retrieves metadata about collections in Metabase without modifying, executing, or deleting any data. It is a read-only operation with minimal blast radius if misused by an AI agent—the worst case being information disclosure of collection names and organization structure.

From the tool's definition Tool name 'list_collections' and description 'List all collections in Metabase' indicate a query/retrieval operation with no modification or execution of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_collections safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase Analytics Integration Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_collections, this is the rule to start with:

list_collections Allowed

list_collections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every list_collections call is checked against it from then on.

FAQ

Questions about list_collections

What does the list_collections tool do? +

List all collections in Metabase. It is categorised as a Read tool in the Metabase Analytics Integration Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_collections? +

Register the Metabase Analytics Integration Server MCP server in PolicyLayer and add a rule for list_collections: 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 Analytics Integration Server. Nothing to install.

What risk level is list_collections? +

list_collections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_collections? +

Yes. Add a rate_limit block to the list_collections 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 list_collections completely? +

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

list_collections is provided by the Metabase Analytics Integration Server MCP server (zsh52013148087/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metabase Analytics Integration Server, and thousands of servers like it.

This server

All 16 Metabase Analytics Integration Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →