Analyze startup programs for suspicious entries
AI agents call analyze_startup_programs 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 analyzes information about startup programs to identify suspicious entries. It performs read-only inspection of system configuration data. While the analysis could surface security concerns, the tool itself does not execute, modify, delete, or move anything—it only queries and evaluates startup program data.
From the tool's definition Tool name 'analyze_startup_programs' and description 'Analyze startup programs for suspicious entries' indicate inspection and analysis of existing system data without modification or execution of programs.
Attacks that exploit this kind of access
Analyze startup programs for suspicious entries. 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 analyze_startup_programs: 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.
analyze_startup_programs 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 analyze_startup_programs 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 analyze_startup_programs. 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.
analyze_startup_programs 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 →