Run an automated test scenario based on natural language description.
AI agents invoke run_test_scenario to trigger actions in MCP Appium. 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 automated operations on Android devices whose effects depend entirely on the natural language scenario provided. An AI agent could be prompted to execute unintended actions on a mobile device (e.g., unauthorized transactions, data exfiltration, sending messages).
From the tool's definition Tool executes automated test scenarios based on natural language descriptions; Appium automates Android device interactions including screen actions, text input, and navigation.
Attacks that exploit this kind of access
Run an automated test scenario based on natural language description. It is categorised as a Execute tool in the MCP Appium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Appium MCP server in PolicyLayer and add a rule for run_test_scenario: 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. Nothing to install.
run_test_scenario 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 run_test_scenario 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 run_test_scenario. 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.
run_test_scenario is provided by the MCP Appium MCP server (supremehyo/appium-mcp-claude-android). 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 →