# get_minifilters

Run fltmc filters and instances and return raw parsed lines.

Agent View of the PolicyLayer registry record for `get_minifilters`. HTML page: https://policylayer.com/tools/0xhackerfren-procmon-mcp/get-minifilters

## Facts

- Tool: `get_minifilters`
- Server: Procmon (`0xhackerfren/procmon-mcp`) — https://policylayer.com/tools/0xhackerfren-procmon-mcp.md
- Homepage: https://github.com/0xhackerfren/ProcMon-MCP
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_minifilters",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Procmon:

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

## Other tools on Procmon (17)

- `request_elevation` — Execute — https://policylayer.com/tools/0xhackerfren-procmon-mcp/request-elevation.md
- `start_etw_trace` — Execute — https://policylayer.com/tools/0xhackerfren-procmon-mcp/start-etw-trace.md
- `stop_etw_trace` — Execute — https://policylayer.com/tools/0xhackerfren-procmon-mcp/stop-etw-trace.md
- `timed_capture` — Execute — https://policylayer.com/tools/0xhackerfren-procmon-mcp/timed-capture.md
- `analyze_pe` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/analyze-pe.md
- `capture_snapshot` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/capture-snapshot.md
- `check_elevation` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/check-elevation.md
- `find_pe_files` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/find-pe-files.md
- `get_network_connections` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/get-network-connections.md
- `get_process_details` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/get-process-details.md
- `get_security_events` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/get-security-events.md
- `get_system_info` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/get-system-info.md
- `list_drivers` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/list-drivers.md
- `list_etw_providers` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/list-etw-providers.md
- `list_processes` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/list-processes.md
- `list_services` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/list-services.md
- `query_event_log` — Read — https://policylayer.com/tools/0xhackerfren-procmon-mcp/query-event-log.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xhackerfren-procmon-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xhackerfren-procmon-mcp