sync_mirror

Trigger a sync of a pull-mirrored repository

SERVERForgejo SOURCEsqcows/forgejo-mcp

High RISK CLASS

Category Execute

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/sync-mirror.md

WHAT IT DOES

What sync_mirror does on Forgejo

AI agents invoke sync_mirror to trigger actions in Forgejo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why sync_mirror is rated High

Initiates an external operation (repository sync) whose effects depend on mirror configuration and contents.

From the tool's definition Trigger a sync of a pull-mirrored repository

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sync_mirror Rate-limited

sync_mirror stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_mirror": {
      "limits": [
        {
          "counter": "sync_mirror_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sync_mirror

What does the sync_mirror tool do? +

Trigger a sync of a pull-mirrored repository. It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sync_mirror? +

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

sync_mirror is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sync_mirror? +

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

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

sync_mirror 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →