AI agents invoke app_stop to trigger actions in uiautomator2 MCP Server. 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.
The tool executes an external operation (stopping an Android app process) whose effects depend on which app is targeted as an argument. This is Execute rather than Destructive because stopping an app is typically reversible (the app can be restarted), and Destructive applies to irreversible data deletion/destruction.
From the tool's definition Tool name 'app_stop' on an Android automation server that controls device operations. Sibling tools include 'app_start', 'app_install', 'app_clear', indicating this tool performs system-level control actions.
Documented attack patterns abuse exactly the kind of access app_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for app_stop:
{
"version": "1",
"default": "deny",
"tools": {
"app_stop": {
"limits": [
{
"counter": "app_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}app_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.
Free to start. No card required.
app_stop. It is categorised as a Execute tool in the uiautomator2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for app_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 uiautomator2 MCP Server. Nothing to install.
app_stop 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 app_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.
Set action: deny in the PolicyLayer policy for app_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.
app_stop is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.