Low Risk

find_pe_files

Recursively discover PE files under a directory.

How to control find_pe_files ↓

AI agents call find_pe_files to retrieve information from Procmon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs file system enumeration and discovery. It retrieves metadata about PE (Portable Executable) files to report them to the user but does not execute code, modify data, delete files, or trigger financial transactions. The scope is limited to filesystem reads, which is the hallmark of a Read category tool.

From the tool's definition Tool description states 'Recursively discover PE files under a directory' - a purely informational operation that enumerates files without modifying, executing, or deleting anything. The verb 'discover' indicates passive scanning/searching.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Procmon, and nothing reaches the server without passing your rules. This is the rule we recommend for find_pe_files:

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

find_pe_files 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 Procmon — 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.

Go deeper

What does the find_pe_files tool do? +

Recursively discover PE files under a directory. It is categorised as a Read tool in the Procmon MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_pe_files? +

Register the Procmon MCP server in PolicyLayer and add a rule for find_pe_files: 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 Procmon. Nothing to install.

What risk level is find_pe_files? +

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

Can I rate-limit find_pe_files? +

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

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

find_pe_files is provided by the Procmon MCP server (0xhackerfren/procmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Procmon tool call.

Deterministic rules across all 18 Procmon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Procmon tools catalogued and risk-classified — across an index of 42,500+ 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.