move_issue_pin

Move a pinned issue to a new position

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/move-issue-pin.md

WHAT IT DOES

What move_issue_pin does on Forgejo

AI agents use move_issue_pin 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 move_issue_pin is rated Medium

Reorders metadata without creating, deleting, or modifying issue content.

From the tool's definition Move a pinned issue to a new position

Attacks that exploit this kind of access

RECOMMENDED RULE

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

move_issue_pin Rate-limited

move_issue_pin 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": {
    "move_issue_pin": {
      "limits": [
        {
          "counter": "move_issue_pin_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 move_issue_pin call is checked against it from then on.

FAQ

Questions about move_issue_pin

What does the move_issue_pin tool do? +

Move a pinned issue to a new position. 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 move_issue_pin? +

Register the Forgejo MCP server in PolicyLayer and add a rule for move_issue_pin: 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 move_issue_pin? +

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

Can I rate-limit move_issue_pin? +

Yes. Add a rate_limit block to the move_issue_pin 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 move_issue_pin completely? +

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

move_issue_pin 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

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

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