List all saved funnels in the project. Returns funnel IDs and names.
AI agents call list_funnels to retrieve information from Mixpanel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates funnel configurations without modifying, deleting, or executing operations. It is a pure read operation that queries existing data. While Mixpanel is an analytics platform, listing funnels poses minimal risk—it does not execute queries, modify data, or trigger external side effects.
From the tool's definition Tool name is 'list_funnels' and description states 'List all saved funnels in the project. Returns funnel IDs and names.' The verb 'list' and the action of returning metadata about existing funnels indicate read-only retrieval with no side effects.
Attacks that exploit this kind of access
List all saved funnels in the project. Returns funnel IDs and names. It is categorised as a Read tool in the Mixpanel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mixpanel MCP Server MCP server in PolicyLayer and add a rule for list_funnels: 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 Mixpanel MCP Server. Nothing to install.
list_funnels 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_funnels 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_funnels. 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_funnels is provided by the Mixpanel MCP Server MCP server (t-campbell18/mcp-mixpanel). 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 →