list_issue_types

List available issue types

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/list-issue-types.md

WHAT IT DOES

What list_issue_types does on GitHub

AI agents call list_issue_types to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_issue_types is rated Low

This tool queries and returns available issue type metadata without creating, modifying, deleting, or executing any operations. It is a straightforward informational read operation with minimal security risk.

From the tool's definition Tool name 'list_issue_types' and description 'List available issue types' indicate a retrieval operation with no modification or execution of code/commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_issue_types Allowed

list_issue_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_issue_types": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every list_issue_types call is checked against it from then on.

FAQ

Questions about list_issue_types

What does the list_issue_types tool do? +

List available issue types. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_issue_types? +

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

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

Can I rate-limit list_issue_types? +

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

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

list_issue_types 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →