pr-checks
Lists check/status results for a pull request. Returns structured data with check names, states, URLs, and summary counts (passed, failed, pending). When watch=true, polls internally until all checks complete (or timeout).
This record as markdown: /tools/io-github-dave-london-git/pr-checks.md
What pr-checks does on Git
AI agents call pr-checks to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pr-checks is rated Low
This tool performs a pure information retrieval operation on pull request check statuses. Even with the polling behavior (watch=true), it only reads existing status data and does not trigger, execute, or modify any checks, branches, or repository state. It is a Read operation with minimal blast radius if misused—an AI agent could retrieve CI/CD status information but cannot alter checks, commits, or workflows.
From the tool's definition The tool 'Lists check/status results for a pull request' and 'Returns structured data with check names, states, URLs, and summary counts.' It retrieves and queries existing pull request status information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs pr-checks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-checks, this is the rule to start with:
pr-checks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every pr-checks call is checked against it from then on.
Questions about pr-checks
Lists check/status results for a pull request. Returns structured data with check names, states, URLs, and summary counts (passed, failed, pending). When watch=true, polls internally until all checks complete (or timeout). It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git MCP server in PolicyLayer and add a rule for pr-checks: 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. Nothing to install.
pr-checks 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-checks 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-checks. 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-checks is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue