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-npm/pr-list.md
What pr-list does on Npm
AI agents call pr-list to retrieve information from Npm 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
This tool retrieves and queries pull request data with optional filters. It performs no creation, modification, deletion, or execution of external operations. The return of structured metadata (PR number, state, title, author, branch, labels, draft status, merge readiness) is purely informational. Misuse presents minimal risk—an agent cannot harm systems or data through listing operations alone.
From the tool's definition Tool is named 'pr-list' and description explicitly states it 'Lists pull requests' and 'Returns structured list'. The verb 'list' combined with 'returns' indicates query/retrieval with no modification or 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 Npm, 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 Npm, 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 Npm MCP Server, which means it retrieves data without modifying state.
Register the Npm 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 Npm. 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 Npm 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 Npm, and thousands of servers like it.
This server
Across the catalogue