High Risk →

xcode_record_video

Start recording video of a simulator (returns process info)

How to control xcode_record_video ↓

AI agents invoke xcode_record_video 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 executes a simulator recording command with side effects dependent on arguments (which simulator, recording parameters). While not destructive or financial, it performs a real-time operation that cannot be instantly reversed and could be misused to exfiltrate screen content from sensitive simulator sessions.

From the tool's definition 'Start recording video of a simulator' indicates execution of a system-level operation that initiates a video recording process on an iOS simulator. Returns 'process info', confirming it triggers an external operation.

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

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

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

Start recording video of a simulator (returns process info). 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_record_video? +

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

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

Can I rate-limit xcode_record_video? +

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

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

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