posthog_query_trends
Query event trends from PostHog (pageviews, signups, DAU, etc. over time). Returns time-series data. Only works if PostHog is connected.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/posthog-query-trends.md
What posthog_query_trends does on Freedom Mcp
AI agents call posthog_query_trends 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 | — | Events to query. Each: { id: "$pageview", name: "Page Views", math: "total" }. Defaults to $pageview. |
date_to | string | — | End date (default: now) |
interval | string | — | Grouping interval (default: day) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
date_from | string | — | Start date: "-7d", "-30d", "-90d", "2024-01-01" (default: -7d) |
Parameters from the server's own tool schema.
Why posthog_query_trends is rated Low
The tool explicitly queries and returns time-series data from PostHog analytics without creating, modifying, deleting, or executing operations. It is a passive read-only operation on existing telemetry data. No financial transactions, destructive actions, or code execution are involved. Severity is low because misuse would only expose or retrieve analytics insights without operational impact.
From the tool's definition Tool name 'posthog_query_trends' and description 'Query event trends from PostHog (pageviews, signups, DAU, etc. over time). Returns time-series data.' indicate retrieval of analytics data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs posthog_query_trends 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_trends, this is the rule to start with:
posthog_query_trends 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_trends call is checked against it from then on.
Questions about posthog_query_trends
Query event trends from PostHog (pageviews, signups, DAU, etc. over time). Returns time-series data. 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_trends accepts 5 parameters: events, date_to, interval, companyId, date_from. 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_query_trends: 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_trends 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_trends 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_trends. 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_trends 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