AI agents call clevertap_get_real_time_counts 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 queries real-time user activity metrics from CleverTap and returns aggregated counts. It is a read-only operation that retrieves analytics data without side effects. The low severity reflects that misuse would expose non-sensitive aggregate statistics rather than individual user data, financial transactions, or system integrity.
From the tool's definition Tool description explicitly states it 'Get[s] the count of users' with 'breakdown by user type' — purely retrieval operations with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Get the count of users who are actively using the app right now (within the last 5 minutes). Optionally includes a breakdown by user type. 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_real_time_counts: 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_real_time_counts 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_real_time_counts 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_real_time_counts. 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_real_time_counts 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 →