get_journal
AI agents call get_journal 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 server's read-only constraint and the naming convention ('get_*' pattern) strongly indicate this tool retrieves data without modification. Even though the description is empty, the operational context makes it highly likely to be a read operation that queries journal data. Low severity because reading chat history has no destructive or operational side effects.
From the tool's definition Server is explicitly described as 'Read-only bridge' that 'Exposes Cursor's local chat database.' Tool name 'get_journal' follows the read-only pattern of sibling tools (get_active_chat, get_chat, get_journal_summary, list_chats, list_workspaces,…
Attacks that exploit this kind of access
get_journal. 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: 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 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 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. 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 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 →