add_issue_dependency

Make an issue depend on another 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/add-issue-dependency.md

WHAT IT DOES

What add_issue_dependency does on Forgejo

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

Creates reversible metadata linking between issues; modifies issue state but causes no data loss.

From the tool's definition add_issue_dependency: makes issue depend on another issue

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_issue_dependency Rate-limited

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

FAQ

Questions about add_issue_dependency

What does the add_issue_dependency tool do? +

Make an issue depend on another 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 add_issue_dependency? +

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

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

Can I rate-limit add_issue_dependency? +

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

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

add_issue_dependency 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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