sub_issue_write

Change sub-issue

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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/io-github-aifity-omnigit-mcp/sub-issue-write.md

WHAT IT DOES

What sub_issue_write does on GitHub

AI agents use sub_issue_write to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.

RISK

Why sub_issue_write is rated Medium

This tool modifies GitHub sub-issue data reversibly. 'Write' is appropriate because it changes existing data without deleting it or executing arbitrary operations. Severity is medium because modifying issue structure could affect workflows and dependent processes, but the change is reversible and localized to issue metadata rather than code or destructive operations.

From the tool's definition Tool name contains 'write' and description states 'Change sub-issue', indicating modification of existing issue data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sub_issue_write safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sub_issue_write, this is the rule to start with:

sub_issue_write Rate-limited

sub_issue_write 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": {
    "sub_issue_write": {
      "limits": [
        {
          "counter": "sub_issue_write_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 GitHub, apply this rule, and every sub_issue_write call is checked against it from then on.

FAQ

Questions about sub_issue_write

What does the sub_issue_write tool do? +

Change sub-issue. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sub_issue_write? +

Register the GitHub MCP server in PolicyLayer and add a rule for sub_issue_write: 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 GitHub. Nothing to install.

What risk level is sub_issue_write? +

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

Can I rate-limit sub_issue_write? +

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

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

sub_issue_write is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

team_manager_write_memory on Team Manager MCP → The MCP Attack Database →

Guides

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