AI agents call list_actions 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 performs a simple enumeration of Metabase actions. It retrieves metadata about configured actions without side effects. While it could inform an agent about what actions are available to execute via other tools like 'execute_action', the list_actions tool itself only reads and returns information.
From the tool's definition Tool name 'list_actions' and description 'List all actions configured in Metabase' indicate a retrieval operation that queries and returns existing action configurations without modifying, executing, or deleting any data.
Documented attack patterns abuse exactly the kind of access list_actions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Metabase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_actions:
{
"version": "1",
"default": "deny",
"tools": {
"list_actions": {}
}
}list_actions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all actions configured in Metabase. 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_actions: 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_actions 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_actions 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_actions. 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_actions is provided by the Metabase MCP Server MCP server (sazboxai/mcp_metabase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Metabase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Metabase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.