pr-review
Submits a review on a pull request (approve, request-changes, or comment). Returns structured data with the review event, URL, and body echo.
This record as markdown: /tools/io-github-dave-london-docker/pr-review.md
What pr-review does on Docker
AI agents use pr-review to create or update resources in Docker, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docker environment.
Why pr-review is rated Medium
The tool creates a PR review submission (approve, request changes, or comment), which is a reversible write operation on a code repository. It does not delete data or execute code, but it can influence merge decisions, giving it medium severity if misused by an AI agent.
From the tool's definition Submits a review on a pull request (approve, request-changes, or comment)
Attacks that exploit this kind of access
The rule that runs pr-review safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-review, this is the rule to start with:
pr-review 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 Docker, apply this rule, and every pr-review call is checked against it from then on.
Questions about pr-review
Submits a review on a pull request (approve, request-changes, or comment). Returns structured data with the review event, URL, and body echo. It is categorised as a Write tool in the Docker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docker MCP server in PolicyLayer and add a rule for pr-review: 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 Docker. Nothing to install.
pr-review 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-review 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-review. 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-review is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docker, and thousands of servers like it.
This server
Across the catalogue