Low Risk

drivers_list

List installed device drivers

How to control drivers_list ↓

AI agents call drivers_list to retrieve information from Mcp Windows 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 displays a list of installed drivers, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any actions—it simply queries and returns driver information. The low severity reflects minimal risk from misuse, as reading driver information poses no direct security or operational threat.

From the tool's definition Tool name 'drivers_list' and description 'List installed device drivers' indicate a query operation that retrieves system information without modification or execution of external operations.

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

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

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

drivers_list 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 Mcp Windows — 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 drivers_list tool do? +

List installed device drivers. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on drivers_list? +

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

What risk level is drivers_list? +

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

Can I rate-limit drivers_list? +

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

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

drivers_list is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

441 Mcp Windows 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.