Force stop an Android app by package using a profile from config/apps.json.
AI agents invoke android_force_stop_app to trigger actions in DevLab MCP Suite. 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 forcibly terminates a running Android application process. It is an active operation that affects the state of a running process, classifying it as Execute. It doesn't delete data (not Destructive) nor modify persistent data (not Write). Misuse could disrupt active user sessions or cause data loss from unsaved state, warranting medium severity.
From the tool's definition Force stop an Android app by package
Attacks that exploit this kind of access
Force stop an Android app by package using a profile from config/apps.json. It is categorised as a Execute tool in the DevLab MCP Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for android_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 DevLab MCP Suite. Nothing to install.
android_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 android_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 android_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.
android_force_stop_app is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-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 →