adb_at_probe
Run a standard AT diagnostic probe: modem identification, signal quality, network registration, SIM status, and supported bands. Requires root.
This record as markdown: /tools/io-github-fullread-deepadb/adb-at-probe.md
What adb_at_probe does on Deepadb
AI agents invoke adb_at_probe 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_probe is rated High
This tool executes AT (Hayes) commands against a device modem—a real external operation that triggers modem state queries and diagnostic probes. These are not data retrievals but command execution whose effects (modem response capture, diagnostic output) depend on the modem's state and the probe parameters. The root requirement indicates privileged system access.
From the tool's definition Tool 'adb_at_probe' explicitly 'Run[s] a standard AT diagnostic probe' with side effects including modem identification, signal quality, network registration checks, and SIM status queries. It 'Requires root' and executes AT commands on a modem interface.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs adb_at_probe 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_probe, this is the rule to start with:
adb_at_probe 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_probe call is checked against it from then on.
Questions about adb_at_probe
Run a standard AT diagnostic probe: modem identification, signal quality, network registration, SIM status, and supported bands. 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_probe: 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_probe 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_probe 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_probe. 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_probe 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