mixpanel_user_profiles

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/mixpanel-user-profiles.md

WHAT IT DOES

What mixpanel_user_profiles does on Integrations MCP

AI agents call mixpanel_user_profiles to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mixpanel_user_profiles is rated Low

Based on the tool name alone, this appears to be a data retrieval operation querying Mixpanel user profiles. The 'user_profiles' suffix strongly suggests a GET/Read operation rather than Write, Execute, or Destructive action. However, confidence is moderate due to the empty description.

From the tool's definition Tool name 'mixpanel_user_profiles' indicates retrieval of user profile data from Mixpanel; no action verbs suggesting modification (create, update, delete) are present. The description is empty, limiting definitive classification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mixpanel_user_profiles safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mixpanel_user_profiles, this is the rule to start with:

mixpanel_user_profiles Allowed

mixpanel_user_profiles is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mixpanel_user_profiles": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every mixpanel_user_profiles call is checked against it from then on.

FAQ

Questions about mixpanel_user_profiles

What does the mixpanel_user_profiles tool do? +

mixpanel_user_profiles is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mixpanel_user_profiles? +

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

What risk level is mixpanel_user_profiles? +

mixpanel_user_profiles is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mixpanel_user_profiles? +

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

How do I block mixpanel_user_profiles completely? +

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

What MCP server provides mixpanel_user_profiles? +

mixpanel_user_profiles is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →