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-pare-search/pr-checks.md
What pr-checks does on Search
AI agents call pr-checks to retrieve information from Search 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
The tool performs a read-only operation: it fetches and presents check/status data from a pull request. Even though it includes a polling mechanism (watch=true), the internal polling does not execute any external operations or modify state — it simply waits for and retrieves status updates. This is a passive data retrieval operation with no side effects, placing it firmly in the Read category.
From the tool's definition Tool 'Lists check/status results for a pull request' and 'Returns structured data' — it retrieves and queries existing PR status information without modifying or executing any operations.
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 Search, 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 Search, 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 Search MCP Server, which means it retrieves data without modifying state.
Register the Search 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 Search. 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 Search 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 Search, and thousands of servers like it.
This server
Across the catalogue