pr-close

THE RISK

Critical Risk

Why pr-close needs a policy

Closing a PR is an irreversible state change (a closed PR cannot be automatically reopened to its prior state in most workflows), and optional branch deletion is explicitly destructive and unrecoverable. The combination of PR closure and branch deletion makes this a Destructive action with high severity, as it can permanently remove code history and block ongoing work.

From the tool's definition Closes a pull request with an optional comment and optional branch deletion

Documented attack patterns abuse exactly the kind of access pr-close gives an agent:

POLICY

How to control pr-close

PolicyLayer is an MCP gateway — it sits between your AI agents and Cargo, and nothing reaches the server without passing your rules. This is the rule we recommend for pr-close:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pr-close"
  ]
}

pr-close disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Cargo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cargo tools

Destructive clean Runs dotnet clean to remove build outputs and returns structured results. Destructive remove Runs Destructive reset Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep Destructive secret-delete Deletes a repository, organization, or environment GitHub Actions secret. Destructive tag Manages git tags. Supports list (default), create, and delete actions. List returns struct Destructive variable-delete Deletes a repository, organization, or environment GitHub Actions variable. Destructive workspace Manages Terraform workspaces: list, select, create, or delete workspaces. Destructive branch Lists, creates, renames, or deletes branches. Returns structured branch data. Pass

All 202 Cargo tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
Critical-risk tools in Cargo → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about pr-close

What does the pr-close tool do? +

Closes a pull request with an optional comment and optional branch deletion. Returns structured data with PR number, state, URL, and deleted-branch flag. It is categorised as a Destructive tool in the Cargo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pr-close? +

Register the Cargo MCP server in PolicyLayer and add a rule for pr-close: 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.

What risk level is pr-close? +

pr-close is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pr-close? +

Yes. Add a rate_limit block to the pr-close 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.

How do I block pr-close completely? +

Set action: deny in the PolicyLayer policy for pr-close. 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.

What MCP server provides pr-close? +

pr-close 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.

Enforce policy on every Cargo tool call.

Start from Cargo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →