Fetch notices (occurrences) for a specific fault
AI agents call get_honeybadger_notices 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.
The tool retrieves or queries error tracking data from Honeybadger without creating, modifying, deleting, or executing any code. It is a passive read operation that fetches notice information for analysis purposes only. The blast radius is minimal as it only accesses already-existing error tracking metadata within the developer's own monitoring system.
From the tool's definition Tool name 'get_honeybadger_notices' and description 'Fetch notices (occurrences) for a specific fault' indicate a retrieval operation with no data modification capability.
Documented attack patterns abuse exactly the kind of access get_honeybadger_notices 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 get_honeybadger_notices:
{
"version": "1",
"default": "deny",
"tools": {
"get_honeybadger_notices": {}
}
}get_honeybadger_notices 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.
Fetch notices (occurrences) for a specific fault. 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 get_honeybadger_notices: 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.
get_honeybadger_notices 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 get_honeybadger_notices 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 get_honeybadger_notices. 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.
get_honeybadger_notices 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.