Update a user
AI agents use mixpanel_set_user_profile to create or update resources in Mixpanel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mixpanel MCP Server environment.
The tool modifies user profile data in Mixpanel's analytics system. While it changes existing records (user profiles), the changes are reversible—profiles can be re-updated with different values. This makes it a Write operation rather than Destructive.
From the tool's definition Tool description states 'Update a user' and server description indicates it 'update user profiles directly'. This is a data modification operation that creates or modifies user data in Mixpanel reversibly.
Attacks that exploit this kind of access
Update a user. It is categorised as a Write tool in the Mixpanel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mixpanel MCP Server MCP server in PolicyLayer and add a rule for mixpanel_set_user_profile: 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 Server. Nothing to install.
mixpanel_set_user_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mixpanel_set_user_profile 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 mixpanel_set_user_profile. 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.
mixpanel_set_user_profile is provided by the Mixpanel MCP Server MCP server (moonbirdai/mixpanel-mcp-server). 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 →