Get hardware information including CPU architecture, PCI devices, USB devices, and memory hardware.
AI agents call get_hardware_info to retrieve information from Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries hardware information without side effects. It performs diagnostic inspection of system components (CPU, PCI, USB, memory) which is typical of the Read category. The read-only nature of the server and the passive verb 'Get' confirm no state changes occur.
From the tool's definition Tool name 'get_hardware_info' and description 'Get hardware information including CPU architecture, PCI devices, USB devices, and memory hardware' indicate retrieval of system diagnostics data only.
Attacks that exploit this kind of access
Get hardware information including CPU architecture, PCI devices, USB devices, and memory hardware. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux MCP Server MCP server in PolicyLayer and add a rule for get_hardware_info: 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 Linux MCP Server. Nothing to install.
get_hardware_info 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 get_hardware_info 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 get_hardware_info. 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.
get_hardware_info is provided by the Linux MCP Server MCP server (narmaku/linux-mcp-server-archived). 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 →