AI agents call system_drivers to retrieve information from Infra Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval only. The underlying commands (driverquery, lsmod, kextstat) are read-only diagnostic utilities that enumerate loaded drivers and kernel modules. No data is created, modified, deleted, or code executed. The blast radius is minimal—at worst, an attacker could discover driver names to identify system vulnerabilities, but the tool itself causes no harm.
From the tool's definition Tool description explicitly states it "List[s] system drivers" using read-only query commands: driverquery, lsmod, kextstat. These are standard diagnostic commands that retrieve kernel/system module information without modification.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List system drivers. Uses driverquery on Windows, lsmod on Linux, kextstat on macOS. It is categorised as a Read tool in the Infra Ops MCP Server, which means it retrieves data without modifying state.
Register the Infra Ops MCP server in PolicyLayer and add a rule for system_drivers: 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 Infra Ops. Nothing to install.
system_drivers 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 system_drivers 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 system_drivers. 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.
system_drivers is provided by the Infra Ops MCP server (skyvanguard/infra-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →