stop_issue_stopwatch

Stop 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/stop-issue-stopwatch.md

WHAT IT DOES

What stop_issue_stopwatch does on Forgejo

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

Stops a time-tracking stopwatch on an issue; reversible write action affecting issue tracking data.

From the tool's definition Stop an issue stopwatch

Attacks that exploit this kind of access

RECOMMENDED RULE

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

stop_issue_stopwatch Rate-limited

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

FAQ

Questions about stop_issue_stopwatch

What does the stop_issue_stopwatch tool do? +

Stop 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 stop_issue_stopwatch? +

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

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

Can I rate-limit stop_issue_stopwatch? +

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

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

stop_issue_stopwatch 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 →