Read the detailed information of a pending resolution. Returns the full file content, git diff (modification details), and the reason for the resolution.
AI agents call read_pending_resolution 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 retrieves and displays information about pending resolutions—file content, diffs, and metadata—without modifying any data. It is a read-only query operation with no side effects or ability to alter repository state. No data is created, deleted, or executed; only information is accessed.
From the tool's definition Tool name 'read_pending_resolution' and description 'Read the detailed information of a pending resolution. Returns the full file content, git diff (modification details), and the reason for the resolution.' indicate data retrieval with no modifications.
Attacks that exploit this kind of access
Read the detailed information of a pending resolution. Returns the full file content, git diff (modification details), and the reason for the resolution. 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 read_pending_resolution: 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.
read_pending_resolution 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 read_pending_resolution 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 read_pending_resolution. 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.
read_pending_resolution 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 →