github_list_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-list-issues.md

WHAT IT DOES

What github_list_issues does on Integrations MCP

AI agents call github_list_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_list_issues is rated Low

This tool retrieves or lists existing GitHub issues, which is a query operation with no side effects. It does not create, modify, delete, execute code, or transfer funds. The low severity reflects that listing issues poses minimal security risk—it accesses publicly available or authorized repository data without causing irreversible changes.

From the tool's definition Tool name 'github_list_issues' indicates a retrieval operation that queries GitHub issues without modification. The 'list' prefix is characteristic of read-only operations that enumerate data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_list_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_list_issues, this is the rule to start with:

github_list_issues Allowed

github_list_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_list_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_list_issues call is checked against it from then on.

FAQ

Questions about github_list_issues

What does the github_list_issues tool do? +

github_list_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_list_issues? +

Register the Integrations MCP server in PolicyLayer and add a rule for github_list_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_list_issues? +

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

Can I rate-limit github_list_issues? +

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

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

github_list_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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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