posthog_list_events
List all event types tracked in PostHog, ordered by usage. Call this FIRST before building funnels or trends — it shows the actual event names in the user's PostHog. Only works if PostHog is connected.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/posthog-list-events.md
What posthog_list_events does on Freedom Mcp
AI agents call posthog_list_events 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 |
|---|---|---|---|
limit | number | — | Max events to return (default: 50) |
search | string | — | Search events by name |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why posthog_list_events is rated Low
This tool retrieves and queries PostHog event data without side effects. It is informational—used to discover available events before building analytics queries. There is no data modification, deletion, code execution, or financial impact. The recommendation to 'call this FIRST' reinforces its role as a non-destructive information lookup.
From the tool's definition Tool description states it 'List[s] all event types tracked in PostHog' and 'shows the actual event names'.
Attacks that exploit this kind of access
The rule that runs posthog_list_events 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_list_events, this is the rule to start with:
posthog_list_events 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_list_events call is checked against it from then on.
Questions about posthog_list_events
List all event types tracked in PostHog, ordered by usage. Call this FIRST before building funnels or trends — it shows the actual event names in the user's PostHog. 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_list_events accepts 3 parameters: limit, search, companyId. Required: 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_list_events: 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_list_events 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_list_events 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_list_events. 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_list_events 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