launch_application · MCP Emulator Controller MCP

WHAT IT DOES

What launch_application does on MCP Emulator Controller

AI agents invoke launch_application to trigger actions in MCP Emulator Controller. 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 launch_application needs a policy

This tool triggers external operations (app launch) whose actual effects depend on runtime arguments (which app to launch). While not destructive by itself, launching arbitrary applications can have significant side effects including data access, network operations, or other uncontrolled behaviors. This fits Execute rather than Write because it invokes existing code/operations rather than creating/modifying data.

From the tool's definition Tool launches applications on an Android emulator/device ('Launch an application on device'). This executes code/operations on a controlled device whose effects depend on which application is launched and what that application does when started.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_application Rate-limited

launch_application 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": {
    "launch_application": {
      "limits": [
        {
          "counter": "launch_application_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 MCP Emulator Controller, so you can run agents against it safely.

FAQ

Questions about launch_application

What does the launch_application tool do? +

Launch an application on device. It is categorised as a Execute tool in the MCP Emulator Controller MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_application? +

Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for launch_application: 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 MCP Emulator Controller. Nothing to install.

What risk level is launch_application? +

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

Can I rate-limit launch_application? +

Yes. Add a rate_limit block to the launch_application 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 launch_application completely? +

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

launch_application is provided by the MCP Emulator Controller MCP server (teemo4621/mcp-emulator-controller). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.