search_issues

THE RISK

Low Risk

Why search_issues needs a policy

The tool performs a search operation to retrieve and list existing issues and pull requests. Search operations are read-only with no side effects, no code execution, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an agent querying issues cannot cause damage to repositories or data.

From the tool's definition Tool name is 'search_issues' and description states it 'Search for issues and pull requests across GitHub repositories' — this is a query/retrieval operation with no modification or deletion of data.

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

POLICY

How to control search_issues

PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub MCP Server Plus, 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.

Create a free account and register GitHub MCP Server Plus — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub MCP Server Plus tools

Write add_issue_comment Add a comment to an existing issue Write create_branch Create a new branch in a GitHub repository Write create_issue Create a new issue in a GitHub repository Write create_or_update_file Create or update a single file in a GitHub repository Write create_pull_request Create a new pull request in a GitHub repository Write create_repository Create a new GitHub repository in your account Write fork_repository Fork a GitHub repository to your account or specified organization Write push_files_content Push multiple files with direct content to a GitHub repository in a single commit

All 18 GitHub MCP Server Plus tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

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 GitHub MCP Server Plus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_issues? +

Register the GitHub MCP Server Plus 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 GitHub MCP Server Plus. 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 GitHub MCP Server Plus MCP server (phialsbasement/mcp-github-server-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitHub MCP Server Plus tool call.

Start from GitHub MCP Server Plus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →