pr-list
Lists pull requests with optional filters. Returns structured list with PR number, state, title, author, branch, labels, draft status, and merge readiness.
This record as markdown: /tools/io-github-dave-london-pare-search/pr-list.md
What pr-list does on Search
AI agents call pr-list 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-list is rated Low
The pr-list tool performs a query operation that retrieves and formats existing pull request metadata. It has no write, execute, destructive, or financial implications. The only potential concern is information disclosure (e.g., if PR content is sensitive), but listing PR metadata is a standard read-only operation.
From the tool's definition Tool description states it 'Lists pull requests' and 'Returns structured list' — a retrieval operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
The rule that runs pr-list 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-list, this is the rule to start with:
pr-list 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-list call is checked against it from then on.
Questions about pr-list
Lists pull requests with optional filters. Returns structured list with PR number, state, title, author, branch, labels, draft status, and merge readiness. 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-list: 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-list 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-list 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-list. 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-list 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