23 tools from the Mobai MCP Server, categorised by risk level.
View the Mobai policy →get_device Get details about a specific device get_screenshot Capture a fast, low-quality screenshot for LLM visual analysis. Returns the file path to the saved image. Use this for AI/LLM processing only — for... list_apps List installed apps on the device list_devices List all connected Android and iOS devices test_create_case Create a new test case in a project 2/5 test_create_project Create a new test project test_delete_case Delete a test case from a project test_delete_line Delete a line from the .mob script test_get_active Get the currently active test project and its cases. Use this to discover which test cases are available. test_get_script Get the .mob script content for a test case (with 1-based line numbers) test_insert_after Insert a new line after the specified line number in the .mob script test_list_projects List all test projects with their test cases included inline test_rename_case Rename an existing test case test_rename_project Rename an existing test project test_replace_script Replace the entire .mob script for a test case 2/5 test_run Run a test case on a device test_update_line Update a single line in the .mob script execute_dsl Execute a batch of DSL commands on a device. This is the primary tool for all device interaction — tap, type, swipe, observe, launch apps, assertio... 3/5 start_bridge Start the automation bridge on a device. Required before interacting with the device. 3/5 stop_bridge Stop the automation bridge on a device 3/5 The Mobai MCP server exposes 23 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Mobai server.
Mobai tools are categorised as Read (17), Write (2), Destructive (1), Execute (3). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept