New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

input_swipe

Swipe by direction or custom coordinates. Raw x1/y1/x2/y2 are screenshot-space and auto-scaled to device coordinates — see input_tap description for full coordinate space rules.

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/input-swipe.md

What input_swipe does on Claude Mobile

AI agents invoke input_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.

Why input_swipe is rated High

This tool performs a UI gesture (swipe) on a real mobile device or simulator. It triggers external operations on the device whose effects depend on the arguments (coordinates/direction), making it Execute. Severity is medium because a misused swipe could trigger unintended UI actions, navigate to sensitive screens, or dismiss important dialogs, but effects are generally reversible.

From the tool's definition Swipe by direction or custom coordinates. Raw x1/y1/x2/y2 are screenshot-space and auto-scaled to device coordinates

Questions about input_swipe

What does the input_swipe tool do? +

Swipe by direction or custom coordinates. Raw x1/y1/x2/y2 are screenshot-space and auto-scaled to device coordinates — see input_tap description for full coordinate space rules. 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 input_swipe? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for input_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 input_swipe? +

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

Can I rate-limit input_swipe? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Mobile's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.