adb_thermal_snapshot
Capture a thermal and power snapshot: all thermal zone temperatures, per-CPU frequencies and governors, cooling device states, and battery temperature/current draw. Optionally save as a baseline for later comparison.
This record as markdown: /tools/io-github-fullread-deepadb/adb-thermal-snapshot.md
What adb_thermal_snapshot does on Deepadb
AI agents call adb_thermal_snapshot 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_thermal_snapshot is rated Low
This tool reads diagnostic telemetry from the Android device without altering system behavior, device configuration, or data. Capturing thermal/power metrics is a read-only diagnostic operation. Saving a baseline for comparison is still a read operation in terms of device impact—no settings are changed, no code is executed, and no data is destructively modified.
From the tool's definition Tool explicitly uses 'Capture' and 'snapshot' language, describing retrieval of thermal zone temperatures, CPU frequencies, governors, cooling device states, and battery metrics.
Attacks that exploit this kind of access
The rule that runs adb_thermal_snapshot 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_thermal_snapshot, this is the rule to start with:
adb_thermal_snapshot 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_thermal_snapshot call is checked against it from then on.
Questions about adb_thermal_snapshot
Capture a thermal and power snapshot: all thermal zone temperatures, per-CPU frequencies and governors, cooling device states, and battery temperature/current draw. Optionally save as a baseline for later comparison. 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_thermal_snapshot: 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_thermal_snapshot 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_thermal_snapshot 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_thermal_snapshot. 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_thermal_snapshot 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