Create a review on a pull request
AI agents use create_pr_review 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.
Creating a PR review is a reversible write operation—it adds metadata/comments to a pull request without deleting data or executing arbitrary code. The impact is limited to repository documentation/communication artifacts. Severity is medium because while reviews influence development workflow and can block merges, they don't directly execute code, delete data, or move funds.
From the tool's definition Tool description explicitly states 'Create a review on a pull request', which is a create operation that modifies PR state by adding review feedback.
Documented attack patterns abuse exactly the kind of access create_pr_review gives an agent:
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 create_pr_review:
{
"version": "1",
"default": "deny",
"tools": {
"create_pr_review": {
"limits": [
{
"counter": "create_pr_review_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_pr_review 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.
Free to start. No card required.
Create a review on 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 create_pr_review: 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.
create_pr_review 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 create_pr_review 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 create_pr_review. 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.
create_pr_review 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.
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.