Get details of a specific issue in a GitHub repository.
AI agents call get_issue to retrieve information from Server Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | |
owner | string | Yes | |
issue_number | number | Yes |
Parameters from the server's own tool schema.
This tool retrieves metadata about an existing GitHub issue. It performs a query operation without creating, modifying, deleting, or executing any code. The action is read-only and presents no risk of unintended data changes or side effects.
From the tool's definition Tool name 'get_issue' and description 'Get details of a specific issue in a GitHub repository' indicate a data retrieval operation with no modifications 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 Server Github MCP Server, which means it retrieves data without modifying state.
get_issue accepts 3 parameters: repo, owner, issue_number. Required: repo, owner, issue_number. The full parameter table on this page comes from the server's own tool schema.
Register the Server Github 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 Server Github. 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 Server Github MCP server (@iflow-mcp/server-github). 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 →