AI agents call clevertap_get_profiles_cursor 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 user profile data from CleverTap without modifying, deleting, or executing any operations. It is a straightforward pagination mechanism for querying existing data. While user profiles can be sensitive data, the tool itself performs no destructive or modifying actions. The risk is limited to data exposure rather than unintended modifications or deletions.
From the tool's definition The tool 'clevertap_get_profiles_cursor' fetches the next page of user profiles using a cursor. The verb 'fetch' and the action of retrieving paginated profile data indicates this is a read-only operation with no side effects.
Attacks that exploit this kind of access
Fetch the next page of user profiles using a cursor returned from clevertap_get_profiles_by_event. 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_profiles_cursor: 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_profiles_cursor 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_profiles_cursor 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_profiles_cursor. 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_profiles_cursor 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 →