List issues in a GitHub repository with filtering options
AI agents call list_issues to retrieve information from MCP-Brave-Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries existing issues from a repository. The verb 'list' and the lack of any modification, creation, or deletion language confirm this is a read-only operation. No side effects or state changes occur. Severity is low because information exposure about issues is generally low-risk, though context-dependent.
From the tool's definition Tool name 'list_issues' and description 'List issues in a GitHub repository with filtering options' indicates a retrieval operation with no modification or deletion capabilities.
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 MCP-Brave-Search, 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 GitHub repository with filtering options. It is categorised as a Read tool in the MCP-Brave-Search MCP Server, which means it retrieves data without modifying state.
Register the MCP-Brave-Search 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 MCP-Brave-Search. 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 MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Brave-Search, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.