Swipe action, Perform a touch gesture for interactions beyond regular scrolling (e.g., adjust a continuous control such as a slider, flip pages in a carousel, dismiss a notification, swipe-to-delete a list item). For regular content scrolling, use Scroll instead. Use "distance" + "direction" for ...
AI agents invoke Swipe to trigger actions in Web Bridge. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | object | — | Ending point of the swipe gesture (mutually exclusive with distance) |
start | object | — | Starting point of the swipe gesture, if not specified, the center of the page will be used |
repeat | number | — | The number of times to repeat the swipe gesture. 1 for default, 0 for infinite (e.g. endless swipe until the end of the page) |
web.url | string | — | URL to open in new tab (omit to use current page) |
distance | number | — | The distance in pixels to swipe (mutually exclusive with end) |
duration | number | — | Duration of the swipe gesture in milliseconds |
direction | string | — | The direction to swipe (required when using distance). The direction means the direction of the finger swipe. |
web.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
web.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
web.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
web.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
This tool triggers browser/UI automation actions (touch gestures) whose effects depend on context and arguments. It can trigger consequential UI interactions like 'swipe-to-delete a list item' or 'dismiss a notification', making it an Execute-category tool. The effects are context-dependent and could range from benign (flipping carousel pages) to moderately impactful (deleting list items via swipe gesture).
From the tool's definition Swipe action, Perform a touch gesture for interactions beyond regular scrolling (e.g., adjust a continuous control such as a slider, flip pages in a carousel, dismiss a notification, swipe-to-delete a list item)
Risk signalsAccepts URL/endpoint input (web.url) · High parameter count (21 properties)
Attacks that exploit this kind of access
Swipe action, Perform a touch gesture for interactions beyond regular scrolling (e.g., adjust a continuous control such as a slider, flip pages in a carousel, dismiss a notification, swipe-to-delete a list item). For regular content scrolling, use Scroll instead. Use "distance" + "direction" for relative movement, or "start" + "end" for precise endpoint movement.. Parameters: start? (object) - Starting point of the swipe gesture, if not specified, the center of the page will be used; direction? (enum('up', 'down', 'left', 'right')) - The direction to swipe (required when using distance). The direction means the direction of the finger swipe.; distance? (number) - The distance in pixels to swipe (mutually exclusive with end); end? (object) - Ending point of the swipe gesture (mutually exclusive with distance); duration? (number) - Duration of the swipe gesture in milliseconds; repeat? (number) - The number of times to repeat the swipe gesture. 1 for default, 0 for infinite (e.g. endless swipe until the end of the page). It is categorised as a Execute tool in the Web Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Swipe accepts 11 parameters: end, start, repeat, web.url, distance, duration, direction, web.aiActContext, web.waitAfterAction, web.replanningCycleLimit, web.screenshotShrinkFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Web Bridge 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 Web Bridge. Nothing to install.
Swipe is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
Swipe is provided by the Web Bridge MCP server (@midscene/web-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →