Low Risk

get_pull_request

Get details of a single pull request

How to control get_pull_request ↓

What get_pull_request does on Forgejo

AI agents call get_pull_request to retrieve information from Forgejo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_pull_request needs a policy

This tool retrieves information about an existing pull request without modifying, deleting, or executing any operations. It is a read-only query operation with minimal risk; the worst misuse would be unauthorized information disclosure of PR details already accessible to the authenticated user.

From the tool's definition Tool name is 'get_pull_request' and description states 'Get details of a single pull request' - this is a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_pull_request gives an agent:

How to control get_pull_request

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pull_request": {}
  }
}

get_pull_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Forgejo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_pull_request

What does the get_pull_request tool do? +

Get details of a single pull request. It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pull_request? +

Register the Forgejo MCP server in PolicyLayer and add a rule for get_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 Forgejo. Nothing to install.

What risk level is get_pull_request? +

get_pull_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pull_request? +

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

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

get_pull_request is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Forgejo tool call.

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

Free to start. No card required.

103 Forgejo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.