Switch keyboard language on simulator/emulator. Use before input_text for correct layout.
AI agents invoke switch_keyboard to trigger actions in React Native. 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.
This tool triggers an external operation on a simulator/emulator by changing the keyboard language setting. It modifies system/device state (keyboard layout) and has side effects that affect subsequent actions. It's not a simple read, and while the change may be reversible, it's an execution of a device-level action rather than a data write, placing it in the Execute category.
From the tool's definition Switch keyboard language on simulator/emulator. Use before input_text for correct layout.
Attacks that exploit this kind of access
Switch keyboard language on simulator/emulator. Use before input_text for correct layout. It is categorised as a Execute tool in the React Native MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the React Native MCP server in PolicyLayer and add a rule for switch_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 React Native. Nothing to install.
switch_keyboard is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the switch_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.
Set action: deny in the PolicyLayer policy for switch_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.
switch_keyboard is provided by the React Native MCP server (@ohah/react-native-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →