Get comprehensive analytics and statistics about Cursor chats including usage patterns, file activity, programming language distribution, and temporal trends. BEST PRACTICE: Use projectPath parameter for project-specific analytics - this analyzes only conversations that worked on files in that pr...
AI agents call get_conversation_analytics to retrieve information from Cursor Conversations MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and analysis operations without side effects. It aggregates and presents statistics about existing Cursor conversation data, making it a Read operation. The severity is low because the blast radius of misuse is limited to information disclosure about coding patterns and development activity, with no capability to modify, delete, or execute code.
From the tool's definition Tool retrieves 'analytics and statistics' about conversations including 'usage patterns, file activity, programming language distribution, and temporal trends.' No modifications, deletions, or code execution are described.
Documented attack patterns abuse exactly the kind of access get_conversation_analytics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cursor Conversations MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_conversation_analytics:
{
"version": "1",
"default": "deny",
"tools": {
"get_conversation_analytics": {}
}
}get_conversation_analytics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get comprehensive analytics and statistics about Cursor chats including usage patterns, file activity, programming language distribution, and temporal trends. BEST PRACTICE: Use projectPath parameter for project-specific analytics - this analyzes only conversations that worked on files in that project, providing much more relevant insights for understanding coding patterns, file usage, and development activity within a specific codebase. WORKFLOW TIP: Always include. It is categorised as a Read tool in the Cursor Conversations MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor Conversations MCP Server MCP server in PolicyLayer and add a rule for get_conversation_analytics: 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 Cursor Conversations MCP Server. Nothing to install.
get_conversation_analytics 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 get_conversation_analytics 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 get_conversation_analytics. 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.
get_conversation_analytics is provided by the Cursor Conversations MCP Server MCP server (vltansky/cursor-chat-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Cursor Conversations MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Cursor Conversations MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.