posthog_query_funnel
Build and run a funnel analysis in PostHog. Shows step-by-step conversion rates (e.g., signup → onboard → purchase). Only works if PostHog is connected.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/posthog-query-funnel.md
What posthog_query_funnel does on Freedom Mcp
AI agents call posthog_query_funnel to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
events | array | Yes | Funnel steps (minimum 2). Each: { id: "event_name", name: "Display Name" } |
date_to | string | — | End date (default: now) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
date_from | string | — | Start date (default: -30d) |
funnel_window_days | number | — | Days a user has to complete the funnel (default: 14) |
Parameters from the server's own tool schema.
Why posthog_query_funnel is rated Low
This tool queries PostHog analytics data to generate funnel conversion reports. While it executes a query operation (slightly elevated from passive read), it retrieves metrics and conversion data without side effects. However, the dependence on PostHog connectivity and potential for resource-intensive queries affecting analytics systems elevates severity from 'low' to 'medium'.
From the tool's definition Tool name contains 'query' and description states 'Build and run a funnel analysis' and 'Shows step-by-step conversion rates'. These are analytical operations that retrieve and display data without modifying PostHog or downstream systems.
Attacks that exploit this kind of access
The rule that runs posthog_query_funnel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For posthog_query_funnel, this is the rule to start with:
posthog_query_funnel 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 Freedom Mcp, apply this rule, and every posthog_query_funnel call is checked against it from then on.
Questions about posthog_query_funnel
Build and run a funnel analysis in PostHog. Shows step-by-step conversion rates (e.g., signup → onboard → purchase). Only works if PostHog is connected. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
posthog_query_funnel accepts 5 parameters: events, date_to, companyId, date_from, funnel_window_days. Required: events, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for posthog_query_funnel: 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 Freedom Mcp. Nothing to install.
posthog_query_funnel 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 posthog_query_funnel 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 posthog_query_funnel. 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.
posthog_query_funnel is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue