Add labels to an issue
AI agents use add_issue_labels 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 is a Write operation: it modifies issue metadata (labels) in a reversible manner. The impact is limited to adding organizational tags to an issue, which can be easily removed or changed. There is no data deletion, code execution, financial impact, or irreversible damage. Severity is low because mislabeling issues has minimal blast radius and is easily corrected.
From the tool's definition The tool name 'add_issue_labels' and description 'Add labels to an issue' indicates a create/modify operation that adds metadata to an existing issue without deleting or destroying data, and without executing arbitrary code or moving funds.
Documented attack patterns abuse exactly the kind of access add_issue_labels 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 add_issue_labels:
{
"version": "1",
"default": "deny",
"tools": {
"add_issue_labels": {
"limits": [
{
"counter": "add_issue_labels_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_issue_labels 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.
Add labels to an issue. 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 add_issue_labels: 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.
add_issue_labels 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 add_issue_labels 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 add_issue_labels. 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.
add_issue_labels 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.