simulator_type_text · MCP Connect MCP: Risk & Policy

WHAT IT DOES

What simulator_type_text does on MCP Connect

AI agents invoke simulator_type_text 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 simulator_type_text needs a policy

This tool performs an action on an external system (iOS Simulator) by injecting text input into a focused field. It is not merely reading data, but actively interacting with the simulator's UI state, making it an Execute-category tool. Misuse could lead to unintended input being sent to applications running in the simulator.

From the tool's definition Types the specified text into the currently focused input field on the iOS simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_type_text Rate-limited

simulator_type_text 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": {
    "simulator_type_text": {
      "limits": [
        {
          "counter": "simulator_type_text_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 simulator_type_text

What does the simulator_type_text tool do? +

Types the specified text into the currently focused input field on the iOS simulator. 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 simulator_type_text? +

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

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

Can I rate-limit simulator_type_text? +

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

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

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