adb_iio_read
Read raw hardware data from the Linux IIO (Industrial I/O) subsystem. Discovers all IIO devices and reads their current values. On Tensor/Exynos devices, this exposes per-rail power monitors (ODPM) showing real-time power consumption per SoC subsystem (CPU clusters, GPU, display, memory, TPU, GPS...
This record as markdown: /tools/io-github-fullread-deepadb/adb-iio-read.md
What adb_iio_read does on Deepadb
AI agents call adb_iio_read to retrieve information from Deepadb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_iio_read is rated Low
This tool retrieves sensor and power monitoring data without modifying or executing anything. While it requires root access and exposes sensitive hardware telemetry (power consumption patterns), it performs only non-destructive data retrieval.
From the tool's definition Tool description explicitly states it 'Read[s] raw hardware data' and 'reads their current values'. No create, modify, delete, or execute operations are mentioned. The tool queries IIO subsystem sensors and power monitors.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_iio_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_iio_read, this is the rule to start with:
adb_iio_read 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 Deepadb, apply this rule, and every adb_iio_read call is checked against it from then on.
Questions about adb_iio_read
Read raw hardware data from the Linux IIO (Industrial I/O) subsystem. Discovers all IIO devices and reads their current values. On Tensor/Exynos devices, this exposes per-rail power monitors (ODPM) showing real-time power consumption per SoC subsystem (CPU clusters, GPU, display, memory, TPU, GPS, etc.) — data not available through the Android sensor HAL. On other devices, may expose raw accelerometer, gyroscope, magnetometer, or ADC channels. Root required. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_iio_read: 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 Deepadb. Nothing to install.
adb_iio_read 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 adb_iio_read 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 adb_iio_read. 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.
adb_iio_read is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
This server
Across the catalogue