Scan the registry for potential security risks
AI agents call scan_security_risks 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.
The tool performs a security analysis scan of the Windows registry to identify risks. Scanning is inherently a read operation that queries and analyzes existing data without creating, modifying, deleting, or executing any changes. The tool does not execute code, trigger external operations, modify registry entries, or move data — it only retrieves and analyzes registry information.
From the tool's definition Tool name is 'scan_security_risks' and description states 'Scan the registry for potential security risks' — the verb 'scan' indicates a read-only query operation that analyzes registry data without modification.
Attacks that exploit this kind of access
Scan the registry for potential security risks. 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 scan_security_risks: 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.
scan_security_risks 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 scan_security_risks 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 scan_security_risks. 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.
scan_security_risks 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 →