dismiss_keyboard · Phantom MCP: Risk & Policy

WHAT IT DOES

What dismiss_keyboard does on Phantom

AI agents invoke dismiss_keyboard to trigger actions in Phantom. 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 dismiss_keyboard needs a policy

This tool performs an action on an external device (iOS simulator, Android emulator, or real device) by dismissing the software keyboard. It is an interaction/automation action rather than a simple read, write, or destructive operation. The blast radius is low since dismissing a keyboard is a benign UI interaction with no lasting side effects.

From the tool's definition 'Ferme le clavier sur le device actif' (closes the keyboard on the active device) — triggers an external operation on a connected simulator/emulator/device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dismiss_keyboard Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dismiss_keyboard": {
      "limits": [
        {
          "counter": "dismiss_keyboard_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 Phantom, so you can run agents against it safely.

FAQ

Questions about dismiss_keyboard

What does the dismiss_keyboard tool do? +

Ferme le clavier sur le device actif (iOS et Android). No-op si pas de clavier visible. À utiliser après un type_text quand le clavier bloque les boutons en bas. It is categorised as a Execute tool in the Phantom MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dismiss_keyboard? +

Register the Phantom MCP server in PolicyLayer and add a rule for dismiss_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 Phantom. Nothing to install.

What risk level is dismiss_keyboard? +

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

Can I rate-limit dismiss_keyboard? +

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

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

dismiss_keyboard is provided by the Phantom MCP server (nthimpulse/phantom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.