clevertap_send_test_push · Clevertap MCP: Risk & Policy

WHAT IT DOES

What clevertap_send_test_push does on Clevertap

AI agents invoke clevertap_send_test_push 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_send_test_push needs a policy

This tool triggers an external operation — dispatching a push notification to a real device — whose effects depend on the arguments (target device token, message content). It is not merely writing data to a store; it executes an outbound action with immediate real-world impact. Severity is high because misuse could result in spamming or phishing users via push notifications at scale.

From the tool's definition Send a test push notification to a specific device token via the CleverTap dashboard

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clevertap_send_test_push Rate-limited

clevertap_send_test_push 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_send_test_push": {
      "limits": [
        {
          "counter": "clevertap_send_test_push_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_send_test_push

What does the clevertap_send_test_push tool do? +

Send a test push notification to a specific device token via the CleverTap dashboard. 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_send_test_push? +

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

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

Can I rate-limit clevertap_send_test_push? +

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

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

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