android_start_activity · DevLab MCP Suite MCP: Risk & Policy

WHAT IT DOES

What android_start_activity does on DevLab MCP Suite

AI agents invoke android_start_activity 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.

WHY IT NEEDS A POLICY

Why android_start_activity needs a policy

This tool executes Android activities and components based on arguments provided by the caller. Launching arbitrary activities can trigger side effects ranging from opening apps to initiating system operations, API calls, or malicious payloads, depending on what the activity does. This is Execute rather than Write because the effects are determined by executing code/components, not by data modification.

From the tool's definition Tool description states it will "Launch an arbitrary Android component (package/activity)" with optional intent action specification. The word "arbitrary" combined with "Launch" indicates execution of externally-supplied code/components without restriction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

android_start_activity Rate-limited

android_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "android_start_activity": {
      "limits": [
        {
          "counter": "android_start_activity_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DevLab MCP Suite, so you can run agents against it safely.

FAQ

Questions about android_start_activity

What does the android_start_activity tool do? +

Launch an arbitrary Android component (package/activity). Optionally specify an intent action. No config profile required. 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.

How do I enforce a policy on android_start_activity? +

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

What risk level is android_start_activity? +

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

Can I rate-limit android_start_activity? +

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

How do I block android_start_activity completely? +

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

What MCP server provides android_start_activity? +

android_start_activity 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.