AI agents invoke stop_scrcpy to trigger actions in uiautomator2 MCP Server. 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 executes a command to stop a running process (scrcpy), which is an Execute action—it triggers an external operation whose effects depend on the target device state. While not inherently destructive (the process can be restarted), it interrupts device automation and could disrupt active sessions.
From the tool's definition Tool name 'stop_scrcpy' indicates termination of scrcpy (a screen mirroring/control daemon). The sibling tools show this server controls Android devices via uiautomator2, and stopping system services is an executable action with external effects.
Documented attack patterns abuse exactly the kind of access stop_scrcpy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_scrcpy:
{
"version": "1",
"default": "deny",
"tools": {
"stop_scrcpy": {
"limits": [
{
"counter": "stop_scrcpy_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_scrcpy 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.
Free to start. No card required.
stop_scrcpy. It is categorised as a Execute tool in the uiautomator2 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for stop_scrcpy: 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 uiautomator2 MCP Server. Nothing to install.
stop_scrcpy 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 stop_scrcpy 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 stop_scrcpy. 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.
stop_scrcpy is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.