This record as markdown: /tools/sagemcp-sagemcp/github-get-issue.md
What github_get_issue does on Sage MCP
AI agents call github_get_issue to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why github_get_issue is rated Low
This tool retrieves and returns information about a GitHub issue without modifying state, executing code, or causing side effects. It is a straightforward read operation similar to querying or fetching data. The low severity reflects minimal risk even if misused by an AI agent—it can only expose information the authenticated user already has access to.
From the tool's definition Tool name 'github_get_issue' and description 'Get details of a specific issue' indicate retrieval of existing data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs github_get_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_get_issue, this is the rule to start with:
github_get_issue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every github_get_issue call is checked against it from then on.
Questions about github_get_issue
Get details of a specific issue. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for github_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 Sage MCP. Nothing to install.
github_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 github_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 github_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.
github_get_issue is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue