issue_number

The issue number (use when item_type is 'issue' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional)

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/issue-number.md

WHAT IT DOES

What issue_number does on GitHub

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

RISK

Why issue_number is rated Low

This appears to be a parameter/input field rather than a standalone tool. It accepts an issue number as a numeric identifier to be passed to 'add_project_item'. It does not perform any action on its own. The description is essentially a parameter specification, not a tool with side effects. Classifying as Other with low confidence due to the uninformative nature of the description as a standalone tool.

From the tool's definition The tool description says 'The issue number (use when item_type is 'issue' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional)'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

issue_number Rate-limited

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

FAQ

Questions about issue_number

What does the issue_number tool do? +

The issue number (use when item_type is 'issue' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional). 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 issue_number? +

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

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

Can I rate-limit issue_number? +

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

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

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