This record as markdown: /tools/sqcows-forgejo-mcp/merge-pull-request.md
What merge_pull_request does on Forgejo
AI agents use merge_pull_request to create or update resources in Forgejo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
Why merge_pull_request is rated Medium
Merging a pull request creates a commit in the repository and updates branch state. While the merge itself can technically be reverted (revert commit), it is a significant write operation that modifies the repository's commit history and code. The blast radius is high because a malicious agent could merge untrusted or breaking code into critical branches (main, production), disrupting development or deployments.
From the tool's definition Tool description states 'Merge a pull request' — this modifies repository state by integrating code changes into a target branch, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs merge_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 merge_pull_request, this is the rule to start with:
merge_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every merge_pull_request call is checked against it from then on.
Questions about merge_pull_request
Merge a pull request. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for merge_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.
merge_pull_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the merge_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.
Set action: deny in the PolicyLayer policy for merge_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.
merge_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.
More on Forgejo, and thousands of servers like it.
This server
Across the catalogue