Perform a long press at the given coordinates on the remote touchscreen.
AI agents invoke touch_long_press to trigger actions in Mcp Remotetouch. 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 physical interaction (long press) on a remote device's touchscreen via SSH. It triggers external operations on a remote machine whose effects depend on the coordinates provided. A long press can activate context menus, trigger drag operations, delete items, or invoke privileged actions on the remote device.
From the tool's definition Perform a long press at the given coordinates on the remote touchscreen
Attacks that exploit this kind of access
Perform a long press at the given coordinates on the remote touchscreen. It is categorised as a Execute tool in the Mcp Remotetouch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Remotetouch MCP server in PolicyLayer and add a rule for touch_long_press: 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 Remotetouch. Nothing to install.
touch_long_press 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 touch_long_press 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 touch_long_press. 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.
touch_long_press is provided by the Mcp Remotetouch MCP server (signal-slot/mcp-remotetouch). 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 →