adb_at_batch
Send multiple AT commands sequentially and capture all responses. Useful for running a diagnostic sequence. Requires root.
This record as markdown: /tools/io-github-fullread-deepadb/adb-at-batch.md
What adb_at_batch does on Deepadb
AI agents invoke adb_at_batch 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_at_batch is rated High
This tool executes multiple AT commands on a device with root privileges. AT commands can control modem/baseband functions including calls, SMS, network configuration, and hardware settings. Running arbitrary AT command sequences with root access can trigger significant side effects on device hardware and communications, placing it firmly in Execute.
From the tool's definition Send multiple AT commands sequentially and capture all responses... Requires root.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_at_batch 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_at_batch, this is the rule to start with:
adb_at_batch 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_at_batch call is checked against it from then on.
Questions about adb_at_batch
Send multiple AT commands sequentially and capture all responses. Useful for running a diagnostic sequence. Requires root. 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_at_batch: 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_at_batch 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_at_batch 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_at_batch. 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_at_batch 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