Get Windows system health overview from Event Logs.
AI agents call get_windows_system_health to retrieve information from MCP Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic inspection of Windows Event Logs to assess system health status. It accesses existing telemetry and diagnostic data without altering state, executing code, or affecting system resources. The read-only nature and informational purpose place it squarely in the Read category with low severity risk.
From the tool's definition Tool retrieves a 'system health overview from Event Logs' — a read-only query of existing log data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get Windows system health overview from Event Logs. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Log Analyzer MCP server in PolicyLayer and add a rule for get_windows_system_health: 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 MCP Log Analyzer. Nothing to install.
get_windows_system_health 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_windows_system_health 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_windows_system_health. 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_windows_system_health is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →