swipe

Swipe in a direction

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/swipe.md

WHAT IT DOES

What swipe does on Claude Mobile

AI agents invoke swipe to trigger actions in Claude Mobile. 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.

RISK

Why swipe is rated High

Swiping is a device automation action that executes a gesture on a real or simulated mobile device. Its effects depend on the current app context and direction argument — it could navigate screens, dismiss alerts, delete items (e.g., swipe-to-delete), or trigger other UI flows. This is an external operation execution rather than a simple read or write.

From the tool's definition 'Swipe in a direction' — triggers a physical UI gesture on a mobile device via ADB or simctl, causing external device interaction whose effects depend on arguments (e.g., navigation, scrolling, or dismissing content).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swipe safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For swipe, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every swipe call is checked against it from then on.

FAQ

Questions about swipe

What does the swipe tool do? +

Swipe in a direction. It is categorised as a Execute tool in the Claude Mobile 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 Claude Mobile 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 Claude Mobile. 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 Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →