install_application · MCP Emulator Controller MCP

WHAT IT DOES

What install_application does on MCP Emulator Controller

AI agents invoke install_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 install_application needs a policy

Installing an APK executes an installation process that deploys code onto the device. This is more than a write operation because it installs executable software that can run with device permissions. A misused agent could install malicious APKs, making this high severity.

From the tool's definition Install APK file on device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_application Rate-limited

install_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": {
    "install_application": {
      "limits": [
        {
          "counter": "install_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 install_application

What does the install_application tool do? +

Install APK file 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 install_application? +

Register the MCP Emulator Controller MCP server in PolicyLayer and add a rule for install_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 install_application? +

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

Can I rate-limit install_application? +

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

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

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