clevertap_stop_campaign · Clevertap MCP: Risk & Policy

WHAT IT DOES

What clevertap_stop_campaign does on Clevertap

AI agents invoke clevertap_stop_campaign to trigger actions in Clevertap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why clevertap_stop_campaign needs a policy

This tool executes an operational action on CleverTap's campaign infrastructure. Stopping a campaign is an Execute action because it triggers a state change in an external system based on provided arguments. While not destructive (the campaign data persists), it has significant blast radius: an agent could halt critical marketing campaigns, disrupt business operations, or cause revenue impact.

From the tool's definition 'Stop an active running campaign by its numeric ID' - this tool triggers an external operation (stopping a campaign) whose effects depend on the campaign ID argument and cannot be easily reversed without manual intervention.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clevertap_stop_campaign Rate-limited

clevertap_stop_campaign stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_stop_campaign": {
      "limits": [
        {
          "counter": "clevertap_stop_campaign_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_stop_campaign

What does the clevertap_stop_campaign tool do? +

Stop an active running campaign by its numeric ID. It is categorised as a Execute tool in the Clevertap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on clevertap_stop_campaign? +

Register the Clevertap MCP server in PolicyLayer and add a rule for clevertap_stop_campaign: 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_stop_campaign? +

clevertap_stop_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit clevertap_stop_campaign? +

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

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

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