get_minifilters

Run fltmc filters and instances and return raw parsed lines.

SERVERProcmon SOURCE0xhackerfren/procmon-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xhackerfren-procmon-mcp/get-minifilters.md

WHAT IT DOES

What get_minifilters does on Procmon

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

RISK

Why get_minifilters is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_minifilters safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Procmon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_minifilters, this is the rule to start with:

get_minifilters Allowed

get_minifilters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_minifilters": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Procmon, apply this rule, and every get_minifilters call is checked against it from then on.

FAQ

Questions about get_minifilters

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.

KEEP EXPLORING

More on Procmon, and thousands of servers like it.

This server

All 18 Procmon tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →