🎯 [SAFE] List all segments (saved filters) in Metabase. Segments are reusable filters like
AI agents call list_segments 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 simply enumerates saved filters (segments) in Metabase. It performs a query operation that returns data but does not create, modify, delete, or execute anything. The '[SAFE]' tag in the description reinforces that this is a benign read operation. No destructive, financial, or execution risks are present.
From the tool's definition Tool name is 'list_segments' and description states '[SAFE] List all segments (saved filters) in Metabase.' The verb 'list' and the descriptor '[SAFE]' indicate this is a read-only operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
🎯 [SAFE] List all segments (saved filters) in Metabase. Segments are reusable filters 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_segments: 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_segments 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_segments 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_segments. 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_segments 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 →