List issues for a GitHub repository.
AI agents call github_list_issues to retrieve information from Mcp Everything without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves GitHub issue data. It performs a read-only operation with no side effects — it neither creates, modifies, executes code, deletes data, nor moves money. The action is informational only. Severity is low because querying public or accessible repository metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'github_list_issues' and description states 'List issues for a GitHub repository' — a pure retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
List issues for a GitHub repository. It is categorised as a Read tool in the Mcp Everything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Everything 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 Mcp Everything. Nothing to install.
github_list_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 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.
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.
github_list_issues is provided by the Mcp Everything MCP server (wellix260/mcp-everything). 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 →