This record as markdown: /tools/io-github-fullread-deepadb/adb-start-activity.md
What adb_start_activity does on Deepadb
AI agents invoke adb_start_activity 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_activity is rated High
This tool triggers external operations (launching activities/apps) whose effects are determined by the intent or component name arguments provided. The outcome depends entirely on what activity is launched, making it an Execute risk—it could start any app, service, or trigger any intent handler on the device.
From the tool's definition Tool name 'adb_start_activity' and description 'Start an activity or app by intent or component name' indicates execution of arbitrary application launch actions on the connected Android device.
Attacks that exploit this kind of access
The rule that runs adb_start_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_start_activity, this is the rule to start with:
adb_start_activity 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 Deepadb, apply this rule, and every adb_start_activity call is checked against it from then on.
Questions about adb_start_activity
Start an activity or app by intent or component name. 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.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_start_activity: 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.
adb_start_activity 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 adb_start_activity 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 adb_start_activity. 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.
adb_start_activity 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.
Across the catalogue