get_pull_request

Get details of a single pull request

SERVERForgejo SOURCEsqcows/forgejo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/get-pull-request.md

WHAT IT DOES

What get_pull_request does on Forgejo

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

RISK

Why get_pull_request is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_pull_request safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_pull_request, this is the rule to start with:

get_pull_request Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pull_request": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every get_pull_request call is checked against it from then on.

FAQ

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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →