get_windows_event_log_info

Get detailed information about a specific Windows Event Log.

Server MCP Log Analyzer sedwardstx/demomcp
Category Read
Risk class Low
Parameters 00 required

What get_windows_event_log_info does on MCP Log Analyzer

AI agents call get_windows_event_log_info 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.

Why get_windows_event_log_info needs a policy

This tool retrieves and queries information from Windows Event Logs without modifying, executing, or deleting data. It has no side effects and presents minimal risk if misused by an AI agent—at worst, an agent could enumerate log sources or gather diagnostic information already present on the system. Blast radius is limited to information disclosure.

From the tool's definition Tool name 'get_windows_event_log_info' and description 'Get detailed information about a specific Windows Event Log' indicate data retrieval without modification. The verb 'Get' and the action of retrieving 'information' confirm this is a read operation.

Questions about get_windows_event_log_info

What does the get_windows_event_log_info tool do? +

Get detailed information about a specific Windows Event Log. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_windows_event_log_info? +

Register the MCP Log Analyzer MCP server in PolicyLayer and add a rule for get_windows_event_log_info: 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.

What risk level is get_windows_event_log_info? +

get_windows_event_log_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_windows_event_log_info? +

Yes. Add a rate_limit block to the get_windows_event_log_info 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.

How do I block get_windows_event_log_info completely? +

Set action: deny in the PolicyLayer policy for get_windows_event_log_info. 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.

What MCP server provides get_windows_event_log_info? +

get_windows_event_log_info 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.