Get Blue Screen of Death (BSOD) events
AI agents call get_bsod_events to retrieve information from Windows Diagnostics 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 BSOD event data from Windows diagnostics, producing no side effects, data modification, code execution, or destructive actions. It aligns with the Read category pattern of accessing diagnostic information for analysis purposes.
From the tool's definition Tool name 'get_bsod_events' and description 'Get Blue Screen of Death (BSOD) events' indicate retrieval of diagnostic event log data. The verb 'Get' and context of querying historical BSOD information confirms read-only access to existing diagnostic events.
Attacks that exploit this kind of access
Get Blue Screen of Death (BSOD) events. It is categorised as a Read tool in the Windows Diagnostics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows Diagnostics MCP Server MCP server in PolicyLayer and add a rule for get_bsod_events: 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 Windows Diagnostics MCP Server. Nothing to install.
get_bsod_events 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_bsod_events 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_bsod_events. 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_bsod_events is provided by the Windows Diagnostics MCP Server MCP server (jackalterman/windows-diagnostic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →