adb_airplane_mode
Toggle airplane mode on/off. Useful for resetting cellular registration during radio testing.
This record as markdown: /tools/io-github-fullread-deepadb/adb-airplane-mode.md
What adb_airplane_mode does on Deepadb
AI agents invoke adb_airplane_mode to trigger actions in Deepadb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why adb_airplane_mode is rated High
This tool triggers an external device state change (toggling airplane mode), which is a reversible but impactful system-level operation on an Android device. It does not merely read data, nor does it irreversibly destroy data or move money. It executes a system command that changes device connectivity state, affecting all network interfaces simultaneously.
From the tool's definition Toggle airplane mode on/off. Useful for resetting cellular registration during radio testing.
Attacks that exploit this kind of access
The rule that runs adb_airplane_mode 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_airplane_mode, this is the rule to start with:
adb_airplane_mode stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_airplane_mode call is checked against it from then on.
Questions about adb_airplane_mode
Toggle airplane mode on/off. Useful for resetting cellular registration during radio testing. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_airplane_mode: 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_airplane_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_airplane_mode 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_airplane_mode. 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_airplane_mode 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.
Across the catalogue