adb_ril_stop

Stop a RIL capture session. Shows a summary of captured message categories.

SERVERDeepadb SOURCEdeepadb

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-ril-stop.md

WHAT IT DOES

What adb_ril_stop does on Deepadb

AI agents invoke adb_ril_stop 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.

RISK

Why adb_ril_stop is rated High

Stopping a RIL capture session is an Execute action because it runs a command that triggers external operations on the device's radio subsystem. While not destructive (the session can be restarted) or immediately dangerous, misuse could disrupt cellular connectivity or interfere with device radio diagnostics.

From the tool's definition Tool name 'adb_ril_stop' and description 'Stop a RIL capture session' indicate this triggers an action on the Radio Interface Layer (RIL) — a critical subsystem controlling cellular communications on Android devices.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_ril_stop 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_ril_stop, this is the rule to start with:

adb_ril_stop Rate-limited

adb_ril_stop 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_ril_stop": {
      "limits": [
        {
          "counter": "adb_ril_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_ril_stop call is checked against it from then on.

FAQ

Questions about adb_ril_stop

What does the adb_ril_stop tool do? +

Stop a RIL capture session. Shows a summary of captured message categories. 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.

How do I enforce a policy on adb_ril_stop? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_ril_stop: 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.

What risk level is adb_ril_stop? +

adb_ril_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_ril_stop? +

Yes. Add a rate_limit block to the adb_ril_stop 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.

How do I block adb_ril_stop completely? +

Set action: deny in the PolicyLayer policy for adb_ril_stop. 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.

What MCP server provides adb_ril_stop? +

adb_ril_stop 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.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server →stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →