sub_issue_id

The ID of the sub-issue to add. ID is not the same as issue number (number, required)

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

Low RISK CLASS

Category Other

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-id.md

WHAT IT DOES

What sub_issue_id does on GitHub

AI agents call sub_issue_id as a supporting operation in GitHub workflows.

RISK

Why sub_issue_id is rated Low

The provided text describes a parameter (sub_issue_id) rather than a complete tool with its own action. There is insufficient information to determine what the tool itself does. Lowering confidence significantly; classifying as Other due to lack of actionable tool description.

From the tool's definition The description only states 'The ID of the sub-issue to add. ID is not the same as issue number (number, required)' — this appears to be a parameter descriptor, not a standalone tool description.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sub_issue_id Rate-limited

sub_issue_id gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sub_issue_id": {
      "limits": [
        {
          "counter": "sub_issue_id_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR 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_id call is checked against it from then on.

FAQ

Questions about sub_issue_id

What does the sub_issue_id tool do? +

The ID of the sub-issue to add. ID is not the same as issue number (number, required). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on sub_issue_id? +

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

sub_issue_id is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sub_issue_id? +

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

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

sub_issue_id 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

pfsense_report_issue on Pfsense → The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →