AI agents call clevertap_get_event_trend 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 only queries and returns analytics data without modifying user profiles, creating campaigns, executing code, or performing destructive operations. It falls squarely into the Read category as a data retrieval function. Severity is low because the worst-case misuse (requesting event trends for sensitive cohorts) causes only information disclosure, not data modification, execution, or financial impact.
From the tool's definition Tool retrieves event trend data over time with 'daily, weekly, or monthly' aggregation and supports 'polling for async results'.
Attacks that exploit this kind of access
Get a trend of event occurrences over time (daily, weekly, or monthly). Supports polling for async results. 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_event_trend: 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_event_trend 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_event_trend 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_event_trend. 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_event_trend 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 →