New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

wavexis_set_touch_emulation

Enable or disable touch event emulation.

SERVERPypi:wavexis SOURCEMathiasPaulenko/wavexis-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/wavexis-mcp/wavexis-set-touch-emulation.md

What wavexis_set_touch_emulation does on Pypi:wavexis

AI agents invoke wavexis_set_touch_emulation to trigger actions in Pypi: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

Questions about wavexis_set_touch_emulation

What does the wavexis_set_touch_emulation tool do? +

Enable or disable touch event emulation. It is categorised as a Execute tool in the Pypi:wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wavexis_set_touch_emulation? +

Register the Pypi: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 Pypi:wavexis. Nothing to install.

What risk level is wavexis_set_touch_emulation? +

wavexis_set_touch_emulation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wavexis_set_touch_emulation? +

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.

How do I block wavexis_set_touch_emulation completely? +

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.

What MCP server provides wavexis_set_touch_emulation? +

wavexis_set_touch_emulation is provided by the Pypi: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 Pypi:wavexis, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pypi:wavexis's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.