AI agents call clevertap_get_profile 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 and retrieves user profile data from CleverTap without creating, modifying, or deleting anything. It has no side effects beyond data retrieval. While user profile data can be sensitive, the tool itself is a straightforward read operation with minimal blast radius—it cannot be misused to cause irreversible harm or unauthorized changes to the system.
From the tool's definition Tool name is 'clevertap_get_profile' and description states 'Retrieve a user profile' with no mention of modifications, deletions, or side effects. The verb 'Retrieve' explicitly indicates a read-only operation.
Attacks that exploit this kind of access
Retrieve a user profile from CleverTap. Provide at least one of: identity, email, or objectId (GUID). 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →