This record as markdown: /tools/mukul975-mcp-windows-automation/drivers-list.md
What drivers_list does on Mcp Windows
AI agents call drivers_list to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why drivers_list is rated Low
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.
Attacks that exploit this kind of access
The rule that runs drivers_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drivers_list, this is the rule to start with:
drivers_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every drivers_list call is checked against it from then on.
Questions about drivers_list
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.
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.
drivers_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue