wavexis_dom_remove
Remove an element matching a CSS selector from the DOM.
This record as markdown: /tools/wavexis-mcp/wavexis-dom-remove.md
What wavexis_dom_remove does on Wavexis
AI agents call wavexis_dom_remove to permanently remove resources in Wavexis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wavexis_dom_remove is rated Critical
Removing DOM elements is a destructive operation that cannot be trivially undone without full page reload or restoration. While not data deletion in a database sense, it irreversibly modifies the document structure and can break page functionality, lose user input, or alter the rendered UI permanently during the session. This exceeds Write (reversible modification) and qualifies as Destructive.
From the tool's definition Tool name 'wavexis_dom_remove' and description 'Remove an element matching a CSS selector from the DOM' indicate irreversible deletion of DOM elements.
Attacks that exploit this kind of access
The rule that runs wavexis_dom_remove 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_dom_remove, this is the rule to start with:
wavexis_dom_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Wavexis, apply this rule, and every wavexis_dom_remove call is checked against it from then on.
Questions about wavexis_dom_remove
Remove an element matching a CSS selector from the DOM. It is categorised as a Destructive tool in the Wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_dom_remove: 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_dom_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wavexis_dom_remove 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_dom_remove. 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_dom_remove 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