AI agents call list_issues to retrieve information from MCPX MCP Gateway 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 issue data from a repository without creating, modifying, deleting, or executing anything. It is a straightforward read operation with minimal blast radius if misused by an AI agent—the worst outcome would be exposure of issue metadata that may already be accessible through normal repository views.
From the tool's definition Tool name 'list_issues' and description 'List issues in a repository' indicate a retrieval operation with no side effects. The verb 'list' is a classic read operation.
Documented attack patterns abuse exactly the kind of access list_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPX MCP Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for list_issues:
{
"version": "1",
"default": "deny",
"tools": {
"list_issues": {}
}
}list_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List issues in a repository. It is categorised as a Read tool in the MCPX MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the MCPX MCP Gateway MCP server in PolicyLayer and add a rule for 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 MCPX MCP Gateway. Nothing to install.
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 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 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.
list_issues is provided by the MCPX MCP Gateway MCP server (thelunarcompany/lunar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 MCPX MCP Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 MCPX MCP Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.