List campaigns from the CleverTap dashboard (web UI API). Returns richer campaign data than the REST API: status, sent, impressions, clicks, engaged, edit URL, and more. Requires a web session — call clevertap_web_login first. Use this whenever the user asks about campaigns from the UI or dashboard.
AI agents call clevertap_get_campaigns_ui to retrieve information from Clevertap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries campaign information from the CleverTap dashboard via web session. It has no side effects—it only lists existing campaign data with richer detail than the REST API. This is a pure read operation with minimal blast radius; even if an AI agent calls it without authorization, it only exposes existing campaign visibility data.
From the tool's definition Tool name contains 'get_campaigns' and description states 'List campaigns from the CleverTap dashboard'. Returns campaign data without modification: 'status, sent, impressions, clicks, engaged, edit URL, and more'.
Attacks that exploit this kind of access
List campaigns from the CleverTap dashboard (web UI API). Returns richer campaign data than the REST API: status, sent, impressions, clicks, engaged, edit URL, and more. Requires a web session — call clevertap_web_login first. Use this whenever the user asks about campaigns from the UI or dashboard. It is categorised as a Read tool in the Clevertap MCP Server, which means it retrieves data without modifying state.
Register the Clevertap MCP server in PolicyLayer and add a rule for clevertap_get_campaigns_ui: 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_get_campaigns_ui is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the clevertap_get_campaigns_ui 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_get_campaigns_ui. 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_get_campaigns_ui 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 →