pr-update
Updates pull request metadata (title, body, labels, assignees, reviewers, milestone, base branch, projects). Returns structured data with PR number and URL.
This record as markdown: /tools/io-github-dave-london-npm/pr-update.md
What pr-update does on Npm
AI agents use pr-update to create or update resources in Npm, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Npm environment.
Why pr-update is rated Medium
This tool modifies PR metadata reversibly (Write category), not destructively. While it can alter important PR state like base branch or labels, these changes can be undone or corrected. Severity is medium because misconfiguration could disrupt workflows, redirect PRs to wrong base branches, or remove critical reviewers, but the impact is scoped to a single PR and reversible.
From the tool's definition Tool explicitly 'Updates pull request metadata (title, body, labels, assignees, reviewers, milestone, base branch, projects)' — modifies PR attributes reversibly. Does not delete or destroy PRs; changes are editable.
Attacks that exploit this kind of access
The rule that runs pr-update 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-update, this is the rule to start with:
pr-update stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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-update call is checked against it from then on.
Questions about pr-update
Updates pull request metadata (title, body, labels, assignees, reviewers, milestone, base branch, projects). Returns structured data with PR number and URL. It is categorised as a Write tool in the Npm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Npm MCP server in PolicyLayer and add a rule for pr-update: 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-update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pr-update 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-update. 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-update 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