AI agents invoke ping 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.
Ping triggers an external network operation (ICMP requests or similar) from the Android device, which is an Execute-category action. While read-like in intent, it actively initiates network traffic to arbitrary external hosts, giving it medium severity since it could be used to probe internal networks or cause minor disruption.
From the tool's definition Tool name 'ping' and description 'Ping网络主机' (Ping network host) — executes a network connectivity test against an external host via an Android device controlled through ADB.
Documented attack patterns abuse exactly the kind of access ping 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 ping:
{
"version": "1",
"default": "deny",
"tools": {
"ping": {
"limits": [
{
"counter": "ping_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ping 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.
Ping网络主机. 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 ping: 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.
ping 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 ping 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 ping. 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.
ping 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.