New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

posthog_query

Run an ad-hoc HogQL (SQL) query against a PostHog project's events.

SERVERUnClick SOURCE@unclick/mcp-server
High RISK CLASS
Category Execute
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/posthog-query.md

What posthog_query does on UnClick

AI agents invoke posthog_query to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
host string PostHog host (default https://us.posthog.com)
query string Yes HogQL/SQL query (e.g. select count() from events)
api_key string Yes PostHog Personal API key
project_id string PostHog project id (can be a saved default)

Parameters from the server's own tool schema.

Why posthog_query is rated High

This tool executes arbitrary SQL-like queries against a PostHog project. While the primary use case is reading analytics data, the ability to run ad-hoc HogQL/SQL queries means it could execute complex or destructive operations depending on what HogQL supports.

From the tool's definition "Run an ad-hoc HogQL (SQL) query against a PostHog project's events"

Risk signalsAccepts URL/endpoint input (host) · Handles credentials or secrets (api_key)

Questions about posthog_query

What does the posthog_query tool do? +

Run an ad-hoc HogQL (SQL) query against a PostHog project's events. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does posthog_query accept? +

posthog_query accepts 4 parameters: host, query, api_key, project_id. Required: query, api_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on posthog_query? +

Register the UnClick MCP server in PolicyLayer and add a rule for posthog_query: 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 UnClick. Nothing to install.

What risk level is posthog_query? +

posthog_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit posthog_query? +

Yes. Add a rate_limit block to the posthog_query 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.

How do I block posthog_query completely? +

Set action: deny in the PolicyLayer policy for posthog_query. 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.

What MCP server provides posthog_query? +

posthog_query is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on UnClick, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.