AI agents call clevertap_web_session_status 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 session status information without creating, modifying, deleting, or executing anything. It falls squarely into the Read category as a data retrieval operation. Low severity because unauthorized session status checks pose minimal risk; they do not grant access to user data or enable harmful actions directly.
From the tool's definition Tool description states it 'Check[s] whether a web session...has been captured' and 'when it was obtained' — purely informational queries with no modifications, side effects, or code execution.
Attacks that exploit this kind of access
Check whether a web session (cookie + CSRF token) has been captured for a project, and when it was obtained. 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_web_session_status: 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_web_session_status 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_web_session_status 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_web_session_status. 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_web_session_status 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 →