adb_thermal_compare
Compare current thermal/power state against a saved baseline. Reports temperature changes per zone, CPU frequency shifts, and battery drain rate differences.
This record as markdown: /tools/io-github-fullread-deepadb/adb-thermal-compare.md
What adb_thermal_compare does on Deepadb
AI agents call adb_thermal_compare 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_compare is rated Low
The tool retrieves and compares thermal and power metrics against a baseline—purely observational operations with no side effects. It does not execute commands, modify system state, delete data, or trigger external operations. The core verbs are 'compare' and 'reports,' both consistent with data retrieval and analysis.
From the tool's definition Tool description states it "Compare[s] current thermal/power state against a saved baseline" and "Reports temperature changes per zone, CPU frequency shifts, and battery drain rate differences." These are read-only query operations that retrieve and analyze…
Attacks that exploit this kind of access
The rule that runs adb_thermal_compare 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_compare, this is the rule to start with:
adb_thermal_compare 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_compare call is checked against it from then on.
Questions about adb_thermal_compare
Compare current thermal/power state against a saved baseline. Reports temperature changes per zone, CPU frequency shifts, and battery drain rate differences. 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_compare: 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_compare 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_compare 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_compare. 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_compare 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