get_journal_summary
AI agents call get_journal_summary 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.
The tool is part of a read-only bridge that exposes a local chat database. The naming convention ('get_journal_summary') and sibling operations confirm this retrieves/queries existing data without modification, deletion, or execution of arbitrary code. Severity is low due to the read-only nature—data retrieval from a local Cursor chat database poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_journal_summary' and sibling tools (get_active_chat, get_chat, list_chats, list_workspaces, search_chats) are all read-only retrieval operations. Server is explicitly described as 'Read-only bridge'.
Attacks that exploit this kind of access
get_journal_summary. 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 get_journal_summary: 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.
get_journal_summary 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_journal_summary 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_journal_summary. 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_journal_summary 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 →