High Risk →

send-keys-by-ios-predicate

Send text to an element using iOS predicate string (iOS only)

How to control send-keys-by-ios-predicate ↓

AI agents invoke send-keys-by-ios-predicate to trigger actions in MCP Appium Server. 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.

High Risk

This tool triggers an external operation (sending keystrokes/text input to a mobile UI element via Appium) that affects the state of a running iOS application. It's not a simple data read or write to a database, but an execution of an interaction on a live device/simulator.

From the tool's definition Send text to an element using iOS predicate string (iOS only)

Documented attack patterns abuse exactly the kind of access send-keys-by-ios-predicate gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Appium Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send-keys-by-ios-predicate:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "send-keys-by-ios-predicate": {
      "limits": [
        {
          "counter": "send-keys-by-ios-predicate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

send-keys-by-ios-predicate 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.

  1. Create a free account and register MCP Appium Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the send-keys-by-ios-predicate tool do? +

Send text to an element using iOS predicate string (iOS only). It is categorised as a Execute tool in the MCP Appium Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send-keys-by-ios-predicate? +

Register the MCP Appium Server MCP server in PolicyLayer and add a rule for send-keys-by-ios-predicate: 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 Appium Server. Nothing to install.

What risk level is send-keys-by-ios-predicate? +

send-keys-by-ios-predicate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit send-keys-by-ios-predicate? +

Yes. Add a rate_limit block to the send-keys-by-ios-predicate 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 send-keys-by-ios-predicate completely? +

Set action: deny in the PolicyLayer policy for send-keys-by-ios-predicate. 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 send-keys-by-ios-predicate? +

send-keys-by-ios-predicate is provided by the MCP Appium Server MCP server (rahulec08/appium-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Appium Server tool call.

Deterministic rules across all 110 MCP Appium Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

110 MCP Appium Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.