wavexis_tap

Tap an element (touch emulation click).

SERVERWavexis 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-tap.md

WHAT IT DOES

What wavexis_tap does on Wavexis

AI agents invoke wavexis_tap 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.

RISK

Why wavexis_tap is rated High

This tool simulates a touch/click interaction on a browser element, triggering UI actions whose effects depend on what element is tapped. This is a browser automation action (Execute category). Severity is medium because clicking arbitrary elements could trigger form submissions, navigation, or other side effects, but it doesn't inherently delete data or move money.

From the tool's definition Tap an element (touch emulation click)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wavexis_tap 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_tap, this is the rule to start with:

wavexis_tap Rate-limited

wavexis_tap 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wavexis_tap": {
      "limits": [
        {
          "counter": "wavexis_tap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_tap call is checked against it from then on.

FAQ

Questions about wavexis_tap

What does the wavexis_tap tool do? +

Tap an element (touch emulation click). 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.

How do I enforce a policy on wavexis_tap? +

Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_tap: 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.

What risk level is wavexis_tap? +

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

Can I rate-limit wavexis_tap? +

Yes. Add a rate_limit block to the wavexis_tap 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_tap completely? +

Set action: deny in the PolicyLayer policy for wavexis_tap. 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_tap? +

wavexis_tap 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.

KEEP EXPLORING

More on Wavexis, and thousands of servers like it.

This server

All 195 Wavexis tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →