Force stop an Android app (kills background processes).
AI agents invoke force_stop_app to trigger actions in Android 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.
Force stopping an app terminates running processes immediately. This is an Execute action that triggers an external operation (process termination) on the Android device. While it is somewhat reversible (the app can be restarted), it forcefully kills processes which can cause data loss or interrupt active operations. The blast radius is high because misuse could kill critical system or user applications.
From the tool's definition Force stop an Android app (kills background processes)
Attacks that exploit this kind of access
Force stop an Android app (kills background processes). It is categorised as a Execute tool in the Android MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for force_stop_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 Android MCP Server. Nothing to install.
force_stop_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 force_stop_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 force_stop_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.
force_stop_app is provided by the Android MCP Server MCP server (wujie272/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →