AI agents use edit_label 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.
This tool creates or modifies label metadata (name, color, description) in a repository or project context. Changes to labels are reversible—they can be edited again or reverted. While labels can affect issue/PR organization and automation workflows, the impact is scoped to metadata and does not irreversibly delete data, execute code, or trigger external operations.
From the tool's definition Tool name is 'edit_label' and description states 'Edit an existing label', indicating modification of existing data in a reversible manner.
Documented attack patterns abuse exactly the kind of access edit_label 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 edit_label:
{
"version": "1",
"default": "deny",
"tools": {
"edit_label": {
"limits": [
{
"counter": "edit_label_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_label 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.
Edit an existing label. 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 edit_label: 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.
edit_label 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 edit_label 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 edit_label. 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.
edit_label 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.