List forensically important registry keys.
AI agents call forensics_list_registry_keys to retrieve information from Windows Forensics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries registry data for forensic analysis purposes. It retrieves pre-existing registry keys without creating, modifying, deleting, or executing anything. The action is purely informational and read-only, with no side effects.
From the tool's definition Tool name contains 'list' and description states 'List forensically important registry keys' — a retrieval operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access forensics_list_registry_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Windows Forensics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for forensics_list_registry_keys:
{
"version": "1",
"default": "deny",
"tools": {
"forensics_list_registry_keys": {}
}
}forensics_list_registry_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List forensically important registry keys. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows Forensics MCP Server MCP server in PolicyLayer and add a rule for forensics_list_registry_keys: 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 Forensics MCP Server. Nothing to install.
forensics_list_registry_keys 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 forensics_list_registry_keys 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 forensics_list_registry_keys. 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.
forensics_list_registry_keys is provided by the Windows Forensics MCP Server MCP server (x746b/winforensics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Windows Forensics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Windows Forensics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.