Search for issues and pull requests across GitHub repositories
AI agents call search_issues 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 |
|---|---|---|---|
q | string | Yes | |
page | number | — | |
sort | string | — | |
order | string | — | |
per_page | number | — |
Parameters from the server's own tool schema.
This tool retrieves and searches existing data (issues and pull requests) without creating, modifying, or deleting any resources. It has no side effects beyond returning query results. The blast radius of misuse is minimal — an agent could potentially expose public information or perform excessive searches, but cannot alter state or trigger dangerous operations.
From the tool's definition Tool name is 'search_issues' and description states it 'Search for issues and pull requests across GitHub repositories' — purely a query/retrieval operation with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Search for issues and pull requests across GitHub repositories. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
search_issues accepts 5 parameters: q, page, sort, order, per_page. Required: q. 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 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 Server Github. Nothing to install.
search_issues 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 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.
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.
search_issues 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 →