Delete one or more user profiles from CleverTap. Processing occurs during non-business hours. Max 100 IDs per request.
AI agents call clevertap_delete_profile to permanently remove resources in Clevertap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of user profiles is irreversible data destruction. Even though processing is deferred to non-business hours, the action itself cannot be undone and represents permanent loss of customer data. This is more severe than Write (reversible modifications) and qualifies as Destructive.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete one or more user profiles from CleverTap' with no undo mechanism mentioned. Processes up to 100 IDs per request.
Attacks that exploit this kind of access
Delete one or more user profiles from CleverTap. Processing occurs during non-business hours. Max 100 IDs per request. It is categorised as a Destructive tool in the Clevertap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Clevertap MCP server in PolicyLayer and add a rule for clevertap_delete_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.
clevertap_delete_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clevertap_delete_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 clevertap_delete_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.
clevertap_delete_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.
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 →