github_search_issues

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/github-search-issues.md

WHAT IT DOES

What github_search_issues does on Integrations MCP

AI agents call github_search_issues to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_search_issues is rated Low

Searching for issues queries GitHub's issue tracker and retrieves results—a classic Read operation with no side effects. Even in a multi-provider platform, searching public or accessible issues cannot create, modify, delete, or execute code. The blast radius is minimal since the operation only fetches data the requester already has permission to view.

From the tool's definition Tool name is 'github_search_issues'; the 'search' verb indicates data retrieval without modification. The description is empty, but the naming pattern is consistent with other Read operations on this server (e.g., airtable_list_records,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_search_issues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_search_issues, this is the rule to start with:

github_search_issues Allowed

github_search_issues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_search_issues": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every github_search_issues call is checked against it from then on.

FAQ

Questions about github_search_issues

What does the github_search_issues tool do? +

github_search_issues is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_search_issues? +

Register the Integrations MCP server in PolicyLayer and add a rule for github_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 Integrations MCP. Nothing to install.

What risk level is github_search_issues? +

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

Can I rate-limit github_search_issues? +

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

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

github_search_issues is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →