AI agents call pr_dedup_check to retrieve information from Git Steer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
pr_dedup_check performs a read-only check against existing pull requests to prevent duplicate creation. It retrieves data (returns PR info or null) without modifying, deleting, or executing anything. The tool is defensive in nature—intended to be called before creating PRs to avoid unintended duplicates. This is a simple lookup/query operation, clearly in the Read category with low severity.
From the tool's definition Tool description states it 'Check[s] if an open PR with a matching title prefix already exists' and 'Returns the existing PR if found, or null.' This is a query operation with no side effects.
Attacks that exploit this kind of access
Check if an open PR with a matching title prefix already exists. Returns the existing PR if found, or null. Use before creating alert/remediation PRs to avoid duplicates. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.
Register the Git Steer MCP server in PolicyLayer and add a rule for pr_dedup_check: 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 Steer. Nothing to install.
pr_dedup_check 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 pr_dedup_check 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 pr_dedup_check. 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.
pr_dedup_check is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →