Manually link a Cursor conversation to a git commit. Creates a manual link with specified confidence. Use this when the automatic linking missed a connection, or to explicitly associate a conversation with a commit.
AI agents use link_conversation_commit to create or update resources in Cursor Conversations MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor Conversations MCP Server environment.
This tool modifies metadata by creating associations between conversations and commits. While it does not delete or execute code, it writes relational data that could affect downstream analysis, tooling behavior, or developer workflows if manipulated by a compromised agent. The reversibility and lack of direct destructive capability places it in Write rather than Execute or Destructive.
From the tool's definition Tool description states it "Creates a manual link" and "explicitly associate a conversation with a commit," indicating data modification. The action is reversible (links can typically be unlinked or overwritten).
Documented attack patterns abuse exactly the kind of access link_conversation_commit 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 link_conversation_commit:
{
"version": "1",
"default": "deny",
"tools": {
"link_conversation_commit": {
"limits": [
{
"counter": "link_conversation_commit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link_conversation_commit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manually link a Cursor conversation to a git commit. Creates a manual link with specified confidence. Use this when the automatic linking missed a connection, or to explicitly associate a conversation with a commit. It is categorised as a Write tool in the Cursor Conversations MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor Conversations MCP Server MCP server in PolicyLayer and add a rule for link_conversation_commit: 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.
link_conversation_commit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link_conversation_commit 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 link_conversation_commit. 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.
link_conversation_commit 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.