pr-ready
Marks a pull request as ready for review (or converts it back to draft when undo=true). Returns structured data with PR number, state, URL, and resulting draft status.
This record as markdown: /tools/io-github-dave-london-cargo/pr-ready.md
What pr-ready does on Cargo
AI agents use pr-ready to create or update resources in Cargo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cargo environment.
Why pr-ready is rated Medium
This tool modifies the state of a pull request (ready for review or draft), which is a reversible write operation on a code hosting platform. It does not execute code, delete data, or involve financial transactions. Misuse could prematurely expose PRs for review or hide them, but the action is reversible.
From the tool's definition Marks a pull request as ready for review (or converts it back to draft when undo=true)
Attacks that exploit this kind of access
The rule that runs pr-ready safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pr-ready, this is the rule to start with:
pr-ready 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 Cargo, apply this rule, and every pr-ready call is checked against it from then on.
Questions about pr-ready
Marks a pull request as ready for review (or converts it back to draft when undo=true). Returns structured data with PR number, state, URL, and resulting draft status. It is categorised as a Write tool in the Cargo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cargo MCP server in PolicyLayer and add a rule for pr-ready: 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 Cargo. Nothing to install.
pr-ready 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-ready 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-ready. 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-ready is provided by the Cargo 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 Cargo, and thousands of servers like it.
This server
Across the catalogue