fork_project · Mcp Pagure MCP: Risk & Policy

WHAT IT DOES

What fork_project does on Mcp Pagure

AI agents use fork_project 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 fork_project needs a policy

Forking creates a new repository copy in the user's namespace. This is a reversible write operation (the fork can be deleted later). It does not delete data, execute code, or involve finances. Severity is medium because it consumes server resources and creates a new repository entity, but the blast radius is limited.

From the tool's definition Fork a Pagure project to your namespace

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fork_project Rate-limited

fork_project 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": {
    "fork_project": {
      "limits": [
        {
          "counter": "fork_project_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 fork_project

What does the fork_project tool do? +

Fork a Pagure project to your namespace. 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 fork_project? +

Register the Mcp Pagure MCP server in PolicyLayer and add a rule for fork_project: 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 fork_project? +

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

Can I rate-limit fork_project? +

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

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

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

// THE FULL RECORD

fork_project is one line of Mcp Pagure's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →