Lists Cursor chats with summaries, titles, and metadata ordered by recency. HIGHLY RECOMMENDED: Use projectPath parameter to filter conversations by specific project/codebase - this dramatically improves relevance by finding conversations that actually worked on files in that project. Returns con...
AI agents call list_conversations 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 retrieves and queries conversation history data without modifying, deleting, or executing anything. However, the severity is elevated to 'medium' rather than 'low' because the conversation history could contain sensitive development context, proprietary code patterns, API keys mentioned in conversations, debugging traces, or other confidential information that an AI agent could leak or misuse if not…
From the tool's definition Tool description states it 'Lists Cursor chats with summaries, titles, and metadata' and 'Returns conversation IDs for use with get_conversation tool.' The verb 'Lists' and the passive retrieval of conversation history indicate a read-only operation with no…
Documented attack patterns abuse exactly the kind of access list_conversations 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 list_conversations:
{
"version": "1",
"default": "deny",
"tools": {
"list_conversations": {}
}
}list_conversations 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.
Lists Cursor chats with summaries, titles, and metadata ordered by recency. HIGHLY RECOMMENDED: Use projectPath parameter to filter conversations by specific project/codebase - this dramatically improves relevance by finding conversations that actually worked on files in that project. Returns conversation IDs for use with get_conversation tool. WORKFLOW TIP: Start with projectPath filtering for project-specific analysis, then call get_conversation with specific IDs from results. Includes AI-generated summaries by default. Supports natural time filtering (. 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 list_conversations: 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.
list_conversations 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 list_conversations 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 list_conversations. 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.
list_conversations 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.