replace_issue_labels

Replace all of an issue

SERVERForgejo SOURCEsqcows/forgejo-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/replace-issue-labels.md

WHAT IT DOES

What replace_issue_labels does on Forgejo

AI agents use replace_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.

RISK

Why replace_issue_labels is rated Medium

Modifies issue labels reversibly; affects issue metadata and workflows but data remains recoverable.

From the tool's definition Replace all of an issue [labels]

Attacks that exploit this kind of access

RECOMMENDED RULE

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

replace_issue_labels Rate-limited

replace_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "replace_issue_labels": {
      "limits": [
        {
          "counter": "replace_issue_labels_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every replace_issue_labels call is checked against it from then on.

FAQ

Questions about replace_issue_labels

What does the replace_issue_labels tool do? +

Replace all of 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.

How do I enforce a policy on replace_issue_labels? +

Register the Forgejo MCP server in PolicyLayer and add a rule for replace_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.

What risk level is replace_issue_labels? +

replace_issue_labels is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit replace_issue_labels? +

Yes. Add a rate_limit block to the replace_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.

How do I block replace_issue_labels completely? +

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

What MCP server provides replace_issue_labels? +

replace_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.

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

Govern customer-ops agents →Argument validation →Scoped token →