Low Risk

search_issues

Search for issues and pull requests across GitHub repositories

How to control search_issues ↓

What search_issues does on Claude TypeScript MCP Servers

AI agents call search_issues 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 search_issues needs a policy

This is a read-only operation that queries GitHub for information about issues and pull requests. It has no side effects, cannot modify data, and poses minimal security risk. The blast radius of misuse is limited to unauthorized information disclosure about public/accessible GitHub issues.

From the tool's definition Tool name 'search_issues' and description 'Search for issues and pull requests across GitHub repositories' indicate a query/search operation that retrieves data without modifying or deleting anything.

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

How to control search_issues

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 search_issues:

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

search_issues 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 search_issues

What does the search_issues tool do? +

Search for issues and pull requests across GitHub repositories. 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 search_issues? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for search_issues: 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 search_issues? +

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

Can I rate-limit search_issues? +

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

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

search_issues 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.