wavexis_debug_remove_breakpoint

Remove a breakpoint by ID.

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-debug-remove-breakpoint.md

What wavexis_debug_remove_breakpoint does on Wavexis

AI agents invoke wavexis_debug_remove_breakpoint 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_debug_remove_breakpoint is rated High

Removing a breakpoint affects the execution flow of a running debug session. While it could be argued as a Write (modifying debug configuration), its primary effect is on code execution behavior — enabling code to run past previously halted points. This is an Execute-tier action with moderate blast radius since it could allow previously blocked execution paths to proceed unimpeded.

From the tool's definition 'Remove a breakpoint by ID' — modifies the active debugging state of a browser automation session

Questions about wavexis_debug_remove_breakpoint

What does the wavexis_debug_remove_breakpoint tool do? +

Remove a breakpoint by ID. 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_debug_remove_breakpoint? +

Register the Wavexis MCP server in PolicyLayer and add a rule for wavexis_debug_remove_breakpoint: 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_debug_remove_breakpoint? +

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

Can I rate-limit wavexis_debug_remove_breakpoint? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Wavexis's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.