clevertap_upload_events · Clevertap MCP: Risk & Policy

WHAT IT DOES

What clevertap_upload_events does on Clevertap

AI agents use clevertap_upload_events to create or update resources in Clevertap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clevertap environment.

WHY IT NEEDS A POLICY

Why clevertap_upload_events needs a policy

This tool creates and adds new event data to CleverTap's database. It is reversible (events can be queried, analyzed, or deleted separately) and does not execute arbitrary code or delete data. The 'Upload' verb combined with event tracking functionality indicates a Write operation.

From the tool's definition Tool description states 'Upload one or more events for users to CleverTap' and 'track actions like purchases, logins, page views, etc.' This creates new event records in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clevertap_upload_events Rate-limited

clevertap_upload_events stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clevertap_upload_events": {
      "limits": [
        {
          "counter": "clevertap_upload_events_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Clevertap, so you can run agents against it safely.

FAQ

Questions about clevertap_upload_events

What does the clevertap_upload_events tool do? +

Upload one or more events for users to CleverTap. Use this to track actions like purchases, logins, page views, etc. Max 1000 records per call. It is categorised as a Write tool in the Clevertap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clevertap_upload_events? +

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

What risk level is clevertap_upload_events? +

clevertap_upload_events is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clevertap_upload_events? +

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

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

clevertap_upload_events is provided by the Clevertap MCP server (ralphcorleone/clevertap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.