mixpanel_get_funnels
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/mixpanel-get-funnels.md
What mixpanel_get_funnels does on Integrations MCP
AI agents call mixpanel_get_funnels to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mixpanel_get_funnels is rated Low
Mixpanel funnel endpoints retrieve analytics metrics without modifying data. The tool performs a standard query operation to fetch funnel data, which is non-destructive and has no side effects. While the description is empty (reducing confidence slightly), the naming pattern matches sibling tools like 'amplitude_get_event_counts' which are clearly Read operations.
From the tool's definition Tool name 'mixpanel_get_funnels' indicates a retrieval/query operation ('get') against Mixpanel's funnel analytics data. The 'get' verb and lack of mutation language suggest read-only data retrieval.
Attacks that exploit this kind of access
The rule that runs mixpanel_get_funnels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mixpanel_get_funnels, this is the rule to start with:
mixpanel_get_funnels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every mixpanel_get_funnels call is checked against it from then on.
Questions about mixpanel_get_funnels
mixpanel_get_funnels is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for mixpanel_get_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 Integrations MCP. Nothing to install.
mixpanel_get_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 mixpanel_get_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 mixpanel_get_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.
mixpanel_get_funnels is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue