Get Cursor conversations linked to a specific git commit. Returns commit metadata plus linked conversations with confidence scores. Use this to find the discussion context for a commit.
AI agents call get_commit_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 queries historical data (git commits and their associated conversations) to provide context information. It is purely informational with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent could only over-retrieve conversation history, which is already accessible to the user. This is a standard Read operation.
From the tool's definition Tool retrieves and returns commit metadata and linked conversation data ('get', 'returns'). No modification, deletion, execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access get_commit_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 get_commit_conversations:
{
"version": "1",
"default": "deny",
"tools": {
"get_commit_conversations": {}
}
}get_commit_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.
Get Cursor conversations linked to a specific git commit. Returns commit metadata plus linked conversations with confidence scores. Use this to find the discussion context for a commit. 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_commit_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.
get_commit_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 get_commit_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 get_commit_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.
get_commit_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.