AI agents call search_issues to retrieve information from Bugsnag MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search is a read-only operation that retrieves data without side effects. No evidence suggests this tool modifies, deletes, executes code, or performs financial transactions. It fits the 'Read' category as a query operation on Bugsnag error tracking data.
From the tool's definition Tool is named 'search_issues' and described as 'Search for issues using various criteria'. The description and name indicate a query/search operation.
Documented attack patterns abuse exactly the kind of access search_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsnag MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_issues:
{
"version": "1",
"default": "deny",
"tools": {
"search_issues": {}
}
}search_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.
Search for issues using various criteria. It is categorised as a Read tool in the Bugsnag MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bugsnag MCP Server MCP server in PolicyLayer and add a rule for 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 Bugsnag MCP Server. Nothing to install.
search_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 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.
Set action: deny in the PolicyLayer policy for 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.
search_issues is provided by the Bugsnag MCP Server MCP server (tgeselle/bugsnag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bugsnag MCP Server, 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.
11 Bugsnag MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.