clevertap_web_request · Clevertap MCP: Risk & Policy

WHAT IT DOES

What clevertap_web_request does on Clevertap

AI agents invoke clevertap_web_request 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_web_request needs a policy

This tool executes arbitrary authenticated HTTP requests to the CleverTap web API. Since it can target any endpoint not available in the standard REST API, it can trigger a wide range of actions depending on arguments — including potentially destructive or write operations.

From the tool's definition Make an authenticated HTTP request to the CleverTap dashboard (web) API using the session cookie and CSRF token

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clevertap_web_request Rate-limited

clevertap_web_request 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_web_request": {
      "limits": [
        {
          "counter": "clevertap_web_request_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_web_request

What does the clevertap_web_request tool do? +

Make an authenticated HTTP request to the CleverTap dashboard (web) API using the session cookie and CSRF token captured by clevertap_web_login. Use this for endpoints not available in the standard REST API. 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_web_request? +

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

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

Can I rate-limit clevertap_web_request? +

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

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

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