PostHog battery

The PostHog battery covers PostHog's official MCP server: all 44 tools in its registry. The hosted endpoint exposes one feature subset per features query parameter and every tool without it, so the battery names the whole registry.

Writes need posthog-review. The Claude Code and kagent plugin defaults permit every mark, so the person running the session reviews them; another root config must define an Authority permitting the mark.

View the battery source.

Tool behavior#

• Analytics queries, insights, dashboards, error tracking, experiment results, survey statistics, LLM analytics, and event and property definitions hold what the customer's end users produced. They return untrusted internal data.
• The query tools read only: query-run accepts a trends, funnel, or HogQL node and posts it to PostHog's query endpoint.
• docs-search returns public PostHog documentation and sends its query to Inkeep, so its input must be public.
• Creating or updating an insight, a dashboard, or a survey requires trusted internal data and review, and records posthog.changed.
• Feature flag and experiment writes record posthog.sensitive: a flag gates production behaviour, and an experiment owns the flag it launches. Every deletion records posthog.sensitive too.

Limit#

PostHog API keys do not expose per-project reader boundaries to policy, so all analytics reads default to internal. To restrict an agent to a specific project, pin it in your root policy using argument selectors.

switch-organization and switch-project move which project later calls target. They change no PostHog data and carry no effect. Pin one project in a root rule when it must not move.