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-pare-test/pr-update.md
What pr-update does on Test
AI agents use pr-update to create or update resources in Test, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Test environment.
Why pr-update is rated Medium
This tool modifies PR attributes reversibly (title, body, labels, assignees, etc.) but does not delete data or execute code. The changes can be undone by subsequent updates. While it affects development workflow and collaboration, the scope is limited to PR metadata manipulation rather than code execution, resource destruction, or financial operations.
From the tool's definition Tool description explicitly states it 'Updates pull request metadata (title, body, labels, assignees, reviewers, milestone, base branch, projects)'. The verb 'Updates' combined with listed modification targets indicates data modification capability.
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 Test, 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 Test, 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 Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Test 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 Test. 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 Test 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 Test, and thousands of servers like it.
This server
Across the catalogue