android_close_app
Close an app on the Android device (safe method: HOME key + am kill). Never uses am force-stop (corrupts PackageManager). Example: 'com.whatsapp'.
This record as markdown: /tools/io-github-saloprj-dialogbrain/android-close-app.md
What android_close_app does on Dialogbrain
AI agents invoke android_close_app to trigger actions in Dialogbrain. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
package | string | Yes | Android package name to close (e.g., 'com.whatsapp') |
channel_account_id | integer | — | Android device channel_account ID. Omit when the workspace has a single Android device; REQUIRED when it has more than one (e.g. WhatsApp + LINE), else the call |
Parameters from the server's own tool schema.
Why android_close_app is rated High
This tool executes system-level commands on an Android device (simulating HOME key press and running 'am kill') to terminate a running application. It causes side effects on external hardware/OS state, placing it in the Execute category. Misuse could disrupt running apps or user sessions, warranting medium severity.
From the tool's definition 'Close an app on the Android device (safe method: HOME key + am kill)' — triggers external OS-level operations on an Android device
Attacks that exploit this kind of access
The rule that runs android_close_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For android_close_app, this is the rule to start with:
android_close_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every android_close_app call is checked against it from then on.
Questions about android_close_app
Close an app on the Android device (safe method: HOME key + am kill). Never uses am force-stop (corrupts PackageManager). Example: 'com.whatsapp'. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
android_close_app accepts 2 parameters: package, channel_account_id. Required: package. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for android_close_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 Dialogbrain. Nothing to install.
android_close_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_close_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_close_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_close_app is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue