Query user profiles with filtering. Useful for finding users based on profile properties and analyzing user segments.
AI agents call query_profiles to retrieve information from Mixpanel MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user profile data, which is a Read operation. However, severity is medium rather than low because: (1) the queried data likely contains user PII or sensitive behavioral properties that could be misused if an agent over-queries or leaks results, and (2) in aggregate, an agent could extract comprehensive user segments or cohorts that could inform harmful targeting.
From the tool's definition Tool description states 'Query user profiles with filtering' and 'finding users based on profile properties and analyzing user segments' — these are read-only operations that retrieve and filter existing user data without modification or deletion.
Attacks that exploit this kind of access
Query user profiles with filtering. Useful for finding users based on profile properties and analyzing user segments. It is categorised as a Read tool in the Mixpanel MCP MCP Server, which means it retrieves data without modifying state.
Register the Mixpanel MCP server in PolicyLayer and add a rule for query_profiles: 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 Mixpanel MCP. Nothing to install.
query_profiles 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 query_profiles 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 query_profiles. 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.
query_profiles is provided by the Mixpanel MCP server (mendeel/mixpanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →