adb_start_app

Launch an app by package name (resolves and starts the default launcher activity)

SERVERDeepadb SOURCEdeepadb
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-start-app.md

What adb_start_app does on Deepadb

AI agents invoke adb_start_app to trigger actions in Deepadb. 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.

Why adb_start_app is rated High

Starting an app is an Execute action because it triggers the launch of an external process/activity whose effects depend on which app is specified and its permissions/behaviors. While not destructive or financial in itself, it can cause significant side effects (data access, network connections, resource consumption, user interaction hijacking) depending on the target app.

From the tool's definition Tool launches an app by package name, resolving and starting the default launcher activity. This is explicit code/application execution triggered by the tool invocation.

Questions about adb_start_app

What does the adb_start_app tool do? +

Launch an app by package name (resolves and starts the default launcher activity). It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on adb_start_app? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_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 Deepadb. Nothing to install.

What risk level is adb_start_app? +

adb_start_app is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit adb_start_app? +

Yes. Add a rate_limit block to the adb_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.

How do I block adb_start_app completely? +

Set action: deny in the PolicyLayer policy for adb_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.

What MCP server provides adb_start_app? +

adb_start_app is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Deepadb, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Deepadb's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.