AI agents call clevertap_get_dau 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 aggregate user metrics (DAU counts) from CleverTap's analytics. It performs no side effects, makes no modifications to data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an attacker could only access or exfiltrate already-public or internal analytics data. This is a straightforward Read operation.
From the tool's definition Tool name 'clevertap_get_dau' and description state it 'Get Daily Active Users (DAU) count for a given date range' - a retrieval operation that queries existing analytics data without modifying, executing operations, or deleting anything.
Attacks that exploit this kind of access
Get Daily Active Users (DAU) count for a given date range (unique App Launched events). 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_dau: 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_dau 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_dau 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_dau. 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_dau 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 →