wavexis_set_touch_emulation
Enable or disable touch event emulation.
This record as markdown: /tools/wavexis-mcp/wavexis-set-touch-emulation.md
What wavexis_set_touch_emulation does on Wavexis
AI agents invoke wavexis_set_touch_emulation to trigger actions in Wavexis. 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.
Why wavexis_set_touch_emulation is rated High
This tool modifies the browser's runtime behavior by toggling touch event emulation, which is an execution-level action that changes how the browser processes and dispatches input events. It doesn't read data, create/modify stored data, or delete anything — it triggers an operational change in the browser environment. Misuse could cause unexpected behavior in browser automation workflows but has limited blast radius.
From the tool's definition Enable or disable touch event emulation
Attacks that exploit this kind of access
The rule that runs wavexis_set_touch_emulation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_set_touch_emulation, this is the rule to start with:
wavexis_set_touch_emulation 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_set_touch_emulation call is checked against it from then on.
Questions about wavexis_set_touch_emulation
Enable or disable touch event emulation. It is categorised as a Execute tool in the Wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_set_touch_emulation: 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 Wavexis. Nothing to install.
wavexis_set_touch_emulation 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 wavexis_set_touch_emulation 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 wavexis_set_touch_emulation. 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.
wavexis_set_touch_emulation is provided by the Wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wavexis, and thousands of servers like it.
Across the catalogue