Search the Windows registry by keyword
AI agents call search_registry 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 search operation on the Windows registry, which is fundamentally a data retrieval action. It does not create, modify, delete, or execute code. However, severity is elevated to 'medium' rather than 'low' because registry data can contain sensitive system configuration, credentials, installed software details, and security policies that could be exploited if an AI agent misuses the results to…
From the tool's definition Tool name 'search_registry' and description 'Search the Windows registry by keyword' indicate querying/retrieval of registry data without modification.
Attacks that exploit this kind of access
Search the Windows registry by keyword. 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 search_registry: 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.
search_registry 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 search_registry 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 search_registry. 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.
search_registry 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 →