This record as markdown: /tools/wavexis-mcp/wavexis-new-tab.md
What wavexis_new_tab does on Wavexis
AI agents invoke wavexis_new_tab 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_new_tab is rated High
This tool executes a browser action with side effects that depend on execution context. While creating a tab is reversible and relatively benign, it is an Execute category action per the classification rules: it 'runs code, shell commands, browser actions, or triggers external operations.' The severity is medium because an agent misusing this could open many tabs to exhaust resources or navigate to malicious sites,…
From the tool's definition Tool name 'wavexis_new_tab' and description 'Create a new browser tab' indicate direct browser automation that triggers an external operation (tab creation).
Attacks that exploit this kind of access
The rule that runs wavexis_new_tab 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_new_tab, this is the rule to start with:
wavexis_new_tab 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_new_tab call is checked against it from then on.
Questions about wavexis_new_tab
Create a new browser tab. 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_new_tab: 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_new_tab 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_new_tab 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_new_tab. 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_new_tab 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