Get detailed information about a specific event, including full stacktrace and context
AI agents call get_event to retrieve information from Bugsink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing error event data from a Bugsink instance. It has no side effects—it does not create, modify, delete, or execute operations. It falls squarely within the Read category as a data retrieval function. Severity is low because unauthorized access to error logs poses minimal direct risk compared to tools that modify or execute code.
From the tool's definition Tool description states 'Get detailed information about a specific event', which is a retrieval operation. The server description confirms it 'query and analyze errors' and 'viewing detailed error events with stacktraces'.
Documented attack patterns abuse exactly the kind of access get_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_event:
{
"version": "1",
"default": "deny",
"tools": {
"get_event": {}
}
}get_event 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.
Get detailed information about a specific event, including full stacktrace and context. It is categorised as a Read tool in the Bugsink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bugsink MCP Server MCP server in PolicyLayer and add a rule for get_event: 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 Bugsink MCP Server. Nothing to install.
get_event 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_event 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_event. 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_event is provided by the Bugsink MCP Server MCP server (j-shelfwood/bugsink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bugsink 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.
16 Bugsink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.