List conflicts that are pending resolution. Returns a simplified list containing ONLY the file ID and file path. Use read_pending_resolution to get the file content, diff, and reason.
AI agents call list_pending_resolutions to retrieve information from Git Conflict MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about pending conflict resolutions without creating, modifying, executing code, deleting data, or committing financial transactions. It is a straightforward informational query with no side effects, fitting the Read category. Severity is low because listing pending items poses minimal risk—the tool does not execute commands, modify repositories, or delete data.
From the tool's definition Tool description explicitly states it 'List[s] conflicts that are pending resolution' and 'Returns a simplified list containing ONLY the file ID and file path.' The verb 'list' and the read-only nature of returning metadata without modification confirm this…
Attacks that exploit this kind of access
List conflicts that are pending resolution. Returns a simplified list containing ONLY the file ID and file path. Use read_pending_resolution to get the file content, diff, and reason. It is categorised as a Read tool in the Git Conflict MCP MCP Server, which means it retrieves data without modifying state.
Register the Git Conflict MCP server in PolicyLayer and add a rule for list_pending_resolutions: 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 Git Conflict MCP. Nothing to install.
list_pending_resolutions 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_pending_resolutions 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_pending_resolutions. 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_pending_resolutions is provided by the Git Conflict MCP server (mattyatea/git-conflict-mcp). 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 →