List all collections (folders) in Metabase.
AI agents call list_collections to retrieve information from Metabase Mcp Navi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query-like operation to enumerate collections in Metabase. It retrieves metadata about folder structures but does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker gains visibility into collection organization but cannot alter data or perform actions. This is a standard Read category tool.
From the tool's definition Tool name 'list_collections' and description 'List all collections (folders) in Metabase' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all collections (folders) in Metabase. It is categorised as a Read tool in the Metabase Mcp Navi MCP Server, which means it retrieves data without modifying state.
Register the Metabase Mcp Navi 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 Mcp Navi. Nothing to install.
list_collections 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_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.
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.
list_collections is provided by the Metabase Mcp Navi MCP server (manish-coder-1007/metabase-mcp-navi). 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 →