Low Risk

get_issue

Get details of a specific issue in a GitHub repository

How to control get_issue ↓

What get_issue does on Claude TypeScript MCP Servers

AI agents call get_issue to retrieve information from Claude TypeScript MCP Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_issue needs a policy

This tool retrieves issue metadata from GitHub without modifying, creating, or deleting any data. It is a simple query operation that returns information about an existing issue. The low severity reflects minimal blast radius—unauthorized issue details exposure is typically not critical in most development contexts.

From the tool's definition Tool name 'get_issue' and description 'Get details of a specific issue in a GitHub repository' indicate a read-only retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_issue gives an agent:

How to control get_issue

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for get_issue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_issue": {}
  }
}

get_issue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude TypeScript MCP Servers — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_issue

What does the get_issue tool do? +

Get details of a specific issue in a GitHub repository. It is categorised as a Read tool in the Claude TypeScript MCP Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_issue? +

Register the Claude TypeScript MCP Servers 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 Claude TypeScript MCP Servers. Nothing to install.

What risk level is get_issue? +

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

Can I rate-limit get_issue? +

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.

How do I block get_issue completely? +

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.

What MCP server provides get_issue? +

get_issue is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

84 Claude TypeScript MCP Servers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.