item_type

The item's type, either issue or pull_request. Required for 'add_project_item' method. (string, 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/item-type.md

WHAT IT DOES

What item_type does on GitHub

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

RISK

Why item_type is rated Low

This does not appear to be a standalone executable tool but rather a parameter descriptor for another operation ('add_project_item'). It has no independent action or side effect of its own. The description is uninformative as a tool - it describes a string parameter value. Classifying as Other with low confidence due to the ambiguous nature of this entry.

From the tool's definition The tool description says 'The item's type, either issue or pull_request. Required for add_project_item method.' - this appears to be a parameter/field descriptor rather than an independent tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

item_type Rate-limited

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

FAQ

Questions about item_type

What does the item_type tool do? +

The item's type, either issue or pull_request. Required for 'add_project_item' method. (string, 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 item_type? +

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

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

Can I rate-limit item_type? +

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

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

item_type 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

process_item on MCP Chat →renef_jni_type_boolean on Renef → The MCP Attack Database →

Guides

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