posthog_list_persons
List PostHog persons (users) for a project.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/posthog-list-persons.md
What posthog_list_persons does on UnClick
AI agents call posthog_list_persons to retrieve information from UnClick 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 |
|---|---|---|---|
host | string | — | PostHog host (default https://us.posthog.com) |
limit | number | — | Results to return (max 100, default 25) |
search | string | — | Filter persons by email or properties |
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_list_persons is rated Low
This tool retrieves and queries user data from PostHog without creating, modifying, or deleting any records. It is a read-only data retrieval operation that presents minimal risk even if misused by an AI agent, as it only exposes existing user information already stored in the PostHog project.
From the tool's definition Tool name contains 'list' and description states 'List PostHog persons (users)' — a retrieval operation with no modification or side effects.
Risk signalsAccepts URL/endpoint input (host) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs posthog_list_persons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For posthog_list_persons, this is the rule to start with:
posthog_list_persons 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 UnClick, apply this rule, and every posthog_list_persons call is checked against it from then on.
Questions about posthog_list_persons
List PostHog persons (users) for a project. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
posthog_list_persons accepts 5 parameters: host, limit, search, api_key, project_id. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for posthog_list_persons: 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.
posthog_list_persons 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_persons 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_persons. 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_persons 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.
This server
Across the catalogue