AI agents call get_hardware_sensors to retrieve information from Sysprobe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries hardware sensor status without side effects. It retrieves diagnostic information about system state (temperature, fan speeds, battery status) but does not modify, control, or execute any hardware changes. It is purely informational, making it a Read category tool with low severity risk.
From the tool's definition Tool retrieves live sensor data (temperatures, fans, battery status) with no indication of modification capabilities. The description emphasizes 'get' and 'Live sensors' indicating read-only access to hardware monitoring information.
Attacks that exploit this kind of access
Live sensors: temps, fans, battery (category 'temps'/'fans'/'battery'/'all'). It is categorised as a Read tool in the Sysprobe MCP Server, which means it retrieves data without modifying state.
Register the Sysprobe MCP server in PolicyLayer and add a rule for get_hardware_sensors: 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 Sysprobe. Nothing to install.
get_hardware_sensors 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_sensors 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_sensors. 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_sensors is provided by the Sysprobe MCP server (raindancer118/sysprobe-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 →