Low Risk

Get-Lexicon-URL

Return a Mixpanel Lexicon transformations detail URL for an event or property. Provide either event or property along with project_id. If workspace_id is omitted, the tool will choose the 'All project data' workspace. Use this when the user wants to change event/property metadata such as display ...

Part of the Mixpanel server.

Get-Lexicon-URL is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MIXPANEL →

Free to start. No card required.

AI agents call Get-Lexicon-URL to retrieve information from Mixpanel without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though Get-Lexicon-URL only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "Get-Lexicon-URL": {}
  }
}

See the full Mixpanel policy for all 30 tools.

Get this rule live on your own Mixpanel server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MIXPANEL →

View all 30 tools →

These attack patterns abuse exactly the kind of access Get-Lexicon-URL gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so Get-Lexicon-URL only ever does what you allow.

SECURE MIXPANEL →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the Get-Lexicon-URL tool do? +

Return a Mixpanel Lexicon transformations detail URL for an event or property. Provide either event or property along with project_id. If workspace_id is omitted, the tool will choose the 'All project data' workspace. Use this when the user wants to change event/property metadata such as display name and description.. It is categorised as a Read tool in the Mixpanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on Get-Lexicon-URL? +

Register the Mixpanel MCP server in PolicyLayer and add a rule for Get-Lexicon-URL: 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. Nothing to install.

What risk level is Get-Lexicon-URL? +

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

Can I rate-limit Get-Lexicon-URL? +

Yes. Add a rate_limit block to the Get-Lexicon-URL 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 Get-Lexicon-URL completely? +

Set action: deny in the PolicyLayer policy for Get-Lexicon-URL. 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 Get-Lexicon-URL? +

Get-Lexicon-URL is provided by the Mixpanel MCP server (@mixpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mixpanel tool call.

Deterministic rules across all 30 Mixpanel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.