增强版应用启动功能，尝试多种方法解决权限问题
AI agents invoke enhanced_start_app 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.
Starting applications is an Execute category action because it triggers external operations whose effects depend on arguments (which app is launched). Unlike a simple read operation (get_current_activity), this actively initiates processes and changes device state. It is not Destructive (apps can be stopped), not Write (not modifying persistent data structures), not Financial.
From the tool's definition Tool description states it is an enhanced app-starting functionality that attempts multiple methods to resolve permission issues.
Documented attack patterns abuse exactly the kind of access enhanced_start_app 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 enhanced_start_app:
{
"version": "1",
"default": "deny",
"tools": {
"enhanced_start_app": {
"limits": [
{
"counter": "enhanced_start_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}enhanced_start_app 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 enhanced_start_app: 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.
enhanced_start_app 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 enhanced_start_app 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 enhanced_start_app. 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.
enhanced_start_app 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.