High Risk →

xcode_set_hardware_keyboard

Enable/disable hardware keyboard for a simulator

How to control xcode_set_hardware_keyboard ↓

AI agents invoke xcode_set_hardware_keyboard 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 modifies the runtime configuration of an iOS simulator by toggling the hardware keyboard setting. It triggers an external operation (changing simulator input hardware state) that affects the device's behavior. While not purely destructive or financial, it executes a state change on an external system (the simulator), making Execute the most appropriate category.

From the tool's definition Enable/disable hardware keyboard for a simulator

Documented attack patterns abuse exactly the kind of access xcode_set_hardware_keyboard 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 xcode_set_hardware_keyboard:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "xcode_set_hardware_keyboard": {
      "limits": [
        {
          "counter": "xcode_set_hardware_keyboard_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

xcode_set_hardware_keyboard 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 xcode_set_hardware_keyboard tool do? +

Enable/disable hardware keyboard for a simulator. 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 xcode_set_hardware_keyboard? +

Register the MCP Appium Server MCP server in PolicyLayer and add a rule for xcode_set_hardware_keyboard: 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 xcode_set_hardware_keyboard? +

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

Can I rate-limit xcode_set_hardware_keyboard? +

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

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

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