Low Risk

die_scan_directory

Scan directory for executables and analyze with DiE.

How to control die_scan_directory ↓

What die_scan_directory does on Windows Forensics MCP Server

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

Low Risk

Why die_scan_directory needs a policy

This tool scans a directory for executable files and analyzes them using DiE (Detect It Easy), a static analysis tool. It retrieves file information and performs forensic analysis without modifying files, executing code in a production context, deleting data, or affecting financial systems. The action is purely observational/investigative, fitting the Read category.

From the tool's definition Tool name 'die_scan_directory' and description 'Scan directory for executables and analyze with DiE' indicate reading and analyzing existing files. No modification, deletion, execution, or financial operations are performed.

Documented attack patterns abuse exactly the kind of access die_scan_directory gives an agent:

How to control die_scan_directory

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 die_scan_directory:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "die_scan_directory": {}
  }
}

die_scan_directory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Windows Forensics MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about die_scan_directory

What does the die_scan_directory tool do? +

Scan directory for executables and analyze with DiE. It is categorised as a Read tool in the Windows Forensics MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on die_scan_directory? +

Register the Windows Forensics MCP Server MCP server in PolicyLayer and add a rule for die_scan_directory: 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.

What risk level is die_scan_directory? +

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

Can I rate-limit die_scan_directory? +

Yes. Add a rate_limit block to the die_scan_directory 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 die_scan_directory completely? +

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

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

Enforce policy on every Windows Forensics MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.