swipe · MCP Connect MCP: Risk & Policy

WHAT IT DOES

What swipe does on MCP Connect

AI agents invoke swipe to trigger actions in MCP Connect. 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 (gesture interaction) on a running iOS Simulator. It executes a physical-like UI action that can navigate, scroll, dismiss, or trigger app behaviors depending on coordinates — side effects depend entirely on arguments and the simulator's current state. Not destructive by itself, but qualifies as Execute due to triggering external device interactions.

From the tool's definition Performs a swipe gesture on the simulator screen from (x1, y1) to (x2, y2)

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 MCP Connect, so you can run agents against it safely.

FAQ

Questions about swipe

What does the swipe tool do? +

Performs a swipe gesture on the simulator screen from (x1, y1) to (x2, y2). It is categorised as a Execute tool in the MCP Connect 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 MCP Connect 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 MCP Connect. 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 MCP Connect MCP server (plaintest/mcp-connect). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

swipe is one line of MCP Connect's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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