Get details of a specific issue in a GitHub repository.
AI agents call get-issue to retrieve information from GitHub Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries issue metadata from a GitHub repository. It performs a read-only operation that returns information without creating, modifying, deleting, or executing any code. The action is purely informational and poses minimal security risk even if misused by an AI agent, as it cannot alter repository state or trigger external operations.
From the tool's definition Tool name 'get-issue' and description 'Get details of a specific issue in a GitHub repository' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific issue in a GitHub repository. It is categorised as a Read tool in the GitHub Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Enterprise MCP Server MCP server in PolicyLayer and add a rule for get-issue: 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 Enterprise MCP Server. Nothing to install.
get-issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-issue 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.
Set action: deny in the PolicyLayer policy for get-issue. 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.
get-issue is provided by the GitHub Enterprise MCP Server MCP server (lessinthought/github-enterprice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →