swipe · Espresso MCP: Risk & Policy

WHAT IT DOES

What swipe does on Espresso

AI agents invoke swipe to trigger actions in Espresso. 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 needs a policy

This tool triggers an external operation (a UI gesture) on a connected Android device. Swiping can navigate between screens, dismiss alerts, trigger actions, or interact with UI elements in ways that depend on the current app state and arguments. It is an Execute-category action as it performs a browser/device UI action whose effects depend on context.

From the tool's definition Perform a swipe gesture in a specific direction on the connected Android device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

swipe Rate-limited

swipe 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": {
      "limits": [
        {
          "counter": "swipe_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 Espresso, so you can run agents against it safely.

FAQ

Questions about swipe

What does the swipe tool do? +

Perform a swipe gesture in a specific direction on the connected Android device. It is categorised as a Execute tool in the Espresso 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? +

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

What risk level is swipe? +

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

Can I rate-limit swipe? +

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

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

swipe is provided by the Espresso MCP server (vs4vijay/espresso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.