AI agents invoke toggle_mobile_data to trigger actions in Adb. 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.
This tool toggles mobile data connectivity on an Android device via ADB. It executes a device-level system operation that changes network state. While not destructive or financial in nature, it triggers an external operation with real device effects (enabling/disabling internet access), placing it in Execute. Misuse could disrupt connectivity for apps or services running on the device.
From the tool's definition '打开或关闭移动数据' (Toggle mobile data on or off) — triggers an external device operation that changes network connectivity state
Documented attack patterns abuse exactly the kind of access toggle_mobile_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for toggle_mobile_data:
{
"version": "1",
"default": "deny",
"tools": {
"toggle_mobile_data": {
"limits": [
{
"counter": "toggle_mobile_data_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}toggle_mobile_data 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.
Free to start. No card required.
打开或关闭移动数据. It is categorised as a Execute tool in the Adb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adb MCP server in PolicyLayer and add a rule for toggle_mobile_data: 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 Adb. Nothing to install.
toggle_mobile_data 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 toggle_mobile_data 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 toggle_mobile_data. 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.
toggle_mobile_data is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.