clevertap_demerge_profile · Clevertap MCP: Risk & Policy

WHAT IT DOES

What clevertap_demerge_profile does on Clevertap

AI agents use clevertap_demerge_profile 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_demerge_profile needs a policy

Demerging profiles modifies user identity data by splitting previously merged profiles apart. This is a reversible structural change to user records (profiles could theoretically be re-merged), so it falls under Write rather than Destructive.

From the tool's definition Demerge (unmerge) user profiles that were incorrectly merged in CleverTap. Max 100 identities per request.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clevertap_demerge_profile Rate-limited

clevertap_demerge_profile 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_demerge_profile": {
      "limits": [
        {
          "counter": "clevertap_demerge_profile_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_demerge_profile

What does the clevertap_demerge_profile tool do? +

Demerge (unmerge) user profiles that were incorrectly merged in CleverTap. Max 100 identities per request. 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_demerge_profile? +

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

What risk level is clevertap_demerge_profile? +

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

Can I rate-limit clevertap_demerge_profile? +

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

How do I block clevertap_demerge_profile completely? +

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

What MCP server provides clevertap_demerge_profile? +

clevertap_demerge_profile 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.