swipe_screen · MCP Emulator Controller MCP: Risk & Policy

WHAT IT DOES

What swipe_screen does on MCP Emulator Controller

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

This tool executes a physical interaction (swipe gesture) on a device screen, triggering touch input events on the Android emulator/device. It performs an external operation whose effects depend on the arguments (coordinates, direction, speed), potentially navigating apps, dismissing dialogs, or triggering UI actions.

From the tool's definition Simulate swipe gesture on device screen

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

swipe_screen Rate-limited

swipe_screen 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": {
    "swipe_screen": {
      "limits": [
        {
          "counter": "swipe_screen_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 swipe_screen

What does the swipe_screen tool do? +

Simulate swipe gesture on device screen. 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 swipe_screen? +

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

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

Can I rate-limit swipe_screen? +

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

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

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