is_pr_merged

Check if a pull request has been merged

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/is-pr-merged.md

WHAT IT DOES

What is_pr_merged does on Forgejo

AI agents call is_pr_merged 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 is_pr_merged is rated Low

Tool queries PR merge status without modifying data or triggering side effects.

From the tool's definition Check if a pull request has been merged

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs is_pr_merged 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 is_pr_merged, this is the rule to start with:

is_pr_merged Allowed

is_pr_merged 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": {
    "is_pr_merged": {}
  }
}

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 is_pr_merged call is checked against it from then on.

FAQ

Questions about is_pr_merged

What does the is_pr_merged tool do? +

Check if a pull request has been merged. 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 is_pr_merged? +

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

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

Can I rate-limit is_pr_merged? +

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

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

is_pr_merged 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

The MCP Attack Database →

Guides

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