Low Risk

get_minifilters

Run fltmc filters and instances and return raw parsed lines.

How to control get_minifilters ↓

AI agents call get_minifilters 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 retrieves and parses the output of fltmc (Filter Manager Control Program) to enumerate currently installed minifilter drivers and their instances. It performs no destructive operations, creates no side effects, and does not execute arbitrary code or commands. The 'fltmc' output is system introspection only.

From the tool's definition get_minifilters runs 'fltmc filters and instances' to 'return raw parsed lines' — a read-only query of Windows minifilter driver state with no modification or execution of commands.

Documented attack patterns abuse exactly the kind of access get_minifilters 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 get_minifilters:

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

get_minifilters 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 get_minifilters tool do? +

Run fltmc filters and instances and return raw parsed lines. 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 get_minifilters? +

Register the Procmon MCP server in PolicyLayer and add a rule for get_minifilters: 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 get_minifilters? +

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

Can I rate-limit get_minifilters? +

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

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

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