List recent faults from Honeybadger
AI agents call list_honeybadger_faults to retrieve information from Honeybadger MCP Server 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 existing fault/error data from Honeybadger without creating, modifying, deleting, or executing any operations. It is a passive data retrieval mechanism typical of read-only API endpoints used for diagnostics and monitoring. The blast radius of misuse is minimal — an agent could only retrieve error information already visible to the authenticated user.
From the tool's definition Tool name includes 'list' and description states 'List recent faults' — a retrieval operation with no modification or side effects. Fetches error tracking data from Honeybadger for analysis within the IDE.
Documented attack patterns abuse exactly the kind of access list_honeybadger_faults gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Honeybadger MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_honeybadger_faults:
{
"version": "1",
"default": "deny",
"tools": {
"list_honeybadger_faults": {}
}
}list_honeybadger_faults 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 recent faults from Honeybadger. It is categorised as a Read tool in the Honeybadger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Honeybadger MCP Server MCP server in PolicyLayer and add a rule for list_honeybadger_faults: 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 Honeybadger MCP Server. Nothing to install.
list_honeybadger_faults 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_honeybadger_faults 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_honeybadger_faults. 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_honeybadger_faults is provided by the Honeybadger MCP Server MCP server (vishalzambre/honeybadger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Honeybadger 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.
4 Honeybadger MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.