list_chats
AI agents call list_chats to retrieve information from Cursor Chats Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists chat data from the local Cursor database without modification. It has no side effects and follows the read-only design of the server. The blast radius is minimal since it only exposes existing local data that the user already has access to on their own Windows machine.
From the tool's definition Tool name 'list_chats' with context that this is a 'Read-only bridge' server that 'Exposes Cursor's local chat database via 7 MCP tools'. Sibling tools include get_active_chat, get_chat, get_journal which are all read operations.
Attacks that exploit this kind of access
list_chats. It is categorised as a Read tool in the Cursor Chats Bridge MCP Server, which means it retrieves data without modifying state.
Register the Cursor Chats Bridge MCP server in PolicyLayer and add a rule for list_chats: 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 Chats Bridge. Nothing to install.
list_chats 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_chats 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_chats. 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_chats is provided by the Cursor Chats Bridge MCP server (jherard-fr/cursor-chats-bridge). 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 →