close_pull_request · Mcp Pagure MCP: Risk & Policy

WHAT IT DOES

What close_pull_request does on Mcp Pagure

AI agents use close_pull_request to create or update resources in Mcp Pagure — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pagure environment.

WHY IT NEEDS A POLICY

Why close_pull_request needs a policy

Closing a pull request is a state modification that can be undone by reopening it (reversible). While it affects repository workflow, it does not irreversibly delete data nor execute arbitrary code. The blast radius is medium because closing PRs could disrupt collaboration workflows, but the action is recoverable and scoped to PR management within a specific forge project.

From the tool's definition Tool description states 'Close a pull request without merging' — this modifies the state of a pull request object by closing it, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_pull_request Rate-limited

close_pull_request 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_pull_request": {
      "limits": [
        {
          "counter": "close_pull_request_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Pagure, so you can run agents against it safely.

FAQ

Questions about close_pull_request

What does the close_pull_request tool do? +

Close a pull request without merging. It is categorised as a Write tool in the Mcp Pagure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_pull_request? +

Register the Mcp Pagure MCP server in PolicyLayer and add a rule for close_pull_request: 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 Mcp Pagure. Nothing to install.

What risk level is close_pull_request? +

close_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_pull_request? +

Yes. Add a rate_limit block to the close_pull_request 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 close_pull_request completely? +

Set action: deny in the PolicyLayer policy for close_pull_request. 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 close_pull_request? +

close_pull_request is provided by the Mcp Pagure MCP server (lemenkov/mcp-pagure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.