wavexis_dom_remove_attr
A destructive tool on the Pypi:wavexis MCP server.
This record as markdown: /tools/wavexis-mcp/wavexis-dom-remove-attr.md
What wavexis_dom_remove_attr does on Pypi:wavexis
AI agents call wavexis_dom_remove_attr to permanently remove resources in Pypi:wavexis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wavexis_dom_remove_attr is rated Critical
Tool name suggests removing DOM attributes, which is a destructive, irreversible modification.
From the tool's definition uninformative description
Attacks that exploit this kind of access
The rule that runs wavexis_dom_remove_attr safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi: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_attr, this is the rule to start with:
wavexis_dom_remove_attr 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 Pypi:wavexis, apply this rule, and every wavexis_dom_remove_attr call is checked against it from then on.
Questions about wavexis_dom_remove_attr
wavexis_dom_remove_attr is a destructive tool on the Pypi:wavexis MCP server. It is categorised as a Destructive tool in the Pypi:wavexis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_dom_remove_attr: 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.
wavexis_dom_remove_attr 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_attr 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_attr. 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_attr 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.
Across the catalogue