wavexis_unroute
Remove network routes matching a pattern, or all routes.
This record as markdown: /tools/wavexis-mcp/wavexis-unroute.md
What wavexis_unroute does on Pypi:wavexis
AI agents call wavexis_unroute 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_unroute is rated Critical
An AI agent that decides to call wavexis_unroute doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Pypi:wavexis is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs wavexis_unroute 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_unroute, this is the rule to start with:
wavexis_unroute 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_unroute call is checked against it from then on.
Questions about wavexis_unroute
Remove network routes matching a pattern, or all routes. 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_unroute: 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_unroute 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_unroute 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_unroute. 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_unroute 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