# cs_dbg_set_exception_breakpoints Enable (replace) the debugger's exception breakpoint filters so execution halts when a matching .NET exception is thrown (DAP setExceptionBreakpoints). Pass the filter IDs to enable; call with no filters (or []) to clear them. The result echoes the active filters and lists available_filters — the exception filters the connected adapter advertises (netcoredbg exposes all for every thrown exception and user-unhandled). Requires a running debug session. Not gated (it only configures the debugger). Feature-detected: on an adapter that advertises no exceptionBreakpointFilters it returns a clear "unsupported" message WITHOUT sending anything. Agent View of the PolicyLayer registry record for `cs_dbg_set_exception_breakpoints`. HTML page: https://policylayer.com/tools/breakpoint-mcp/cs-dbg-set-exception-breakpoints ## Facts - Tool: `cs_dbg_set_exception_breakpoints` - Server: Breakpoint (`breakpoint-mcp`) — https://policylayer.com/tools/breakpoint-mcp.md - Install: `npx -y breakpoint-mcp` - Homepage: https://www.npmjs.com/package/breakpoint-mcp - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 1 - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `filters` | array | no | Exception filter IDs to enable (default none = clear). Choose from available_filters in the result (netcoredbg: 'all', 'user-unhandled'). | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "cs_dbg_set_exception_breakpoints", "arguments": {} } } ``` ## Why cs_dbg_set_exception_breakpoints is rated High This tool configures a live debugger to intercept exceptions during execution, directly affecting the control flow of a running debug session. It triggers external debugger operations rather than merely reading or writing data, making Execute the most appropriate category. Misuse could disrupt debugging sessions or cause unintended halts in running processes. From the tool's own definition: "execution halts when a matching .NET exception is thrown (DAP setExceptionBreakpoints)... Requires a running debug session" Risk signals: Bulk/mass operation — affects multiple targets ## Use case AI agents invoke cs_dbg_set_exception_breakpoints to trigger actions in Breakpoint. 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Breakpoint: ```json { "version": "1", "default": "deny", "tools": { "cs_dbg_set_exception_breakpoints": { "limits": [ { "counter": "cs_dbg_set_exception_breakpoints_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Breakpoint (273) - `anim_delete` — Destructive — https://policylayer.com/tools/breakpoint-mcp/anim-delete.md - `anim_remove_key` — Destructive — https://policylayer.com/tools/breakpoint-mcp/anim-remove-key.md - `filesystem_move` — Destructive — https://policylayer.com/tools/breakpoint-mcp/filesystem-move.md - `gd_rename` — Destructive — https://policylayer.com/tools/breakpoint-mcp/gd-rename.md - `inputmap_erase_action` — Destructive — https://policylayer.com/tools/breakpoint-mcp/inputmap-erase-action.md - `mp_wire_rpc` — Destructive — https://policylayer.com/tools/breakpoint-mcp/mp-wire-rpc.md - `node_delete` — Destructive — https://policylayer.com/tools/breakpoint-mcp/node-delete.md - `project_remove_autoload` — Destructive — https://policylayer.com/tools/breakpoint-mcp/project-remove-autoload.md - `resource_save` — Destructive — https://policylayer.com/tools/breakpoint-mcp/resource-save.md - `resource_set_import_settings` — Destructive — https://policylayer.com/tools/breakpoint-mcp/resource-set-import-settings.md - `runtime_node_remove` — Destructive — https://policylayer.com/tools/breakpoint-mcp/runtime-node-remove.md - `runtime_peer_stop` — Destructive — https://policylayer.com/tools/breakpoint-mcp/runtime-peer-stop.md - `scene_close` — Destructive — https://policylayer.com/tools/breakpoint-mcp/scene-close.md - `scene_reload` — Destructive — https://policylayer.com/tools/breakpoint-mcp/scene-reload.md - `shader_set_code` — Destructive — https://policylayer.com/tools/breakpoint-mcp/shader-set-code.md - `tilemap_clear` — Destructive — https://policylayer.com/tools/breakpoint-mcp/tilemap-clear.md - `vcs_restore` — Destructive — https://policylayer.com/tools/breakpoint-mcp/vcs-restore.md - `vcs_stash` — Destructive — https://policylayer.com/tools/breakpoint-mcp/vcs-stash.md - `cs_dbg_attach` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-attach.md - `cs_dbg_continue` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-continue.md - `cs_dbg_launch` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-launch.md - `cs_dbg_restart` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-restart.md - `cs_dbg_set_breakpoints` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-set-breakpoints.md - `cs_dbg_set_variable` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-set-variable.md - `cs_dbg_step` — Execute — https://policylayer.com/tools/breakpoint-mcp/cs-dbg-step.md - `dbg_attach` — Execute — https://policylayer.com/tools/breakpoint-mcp/dbg-attach.md - `dbg_continue` — Execute — https://policylayer.com/tools/breakpoint-mcp/dbg-continue.md - `dbg_data_breakpoints` — Execute — https://policylayer.com/tools/breakpoint-mcp/dbg-data-breakpoints.md - `dbg_goto` — Execute — https://policylayer.com/tools/breakpoint-mcp/dbg-goto.md - `dbg_launch` — Execute — https://policylayer.com/tools/breakpoint-mcp/dbg-launch.md - …and 243 more: https://policylayer.com/tools/breakpoint-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=breakpoint-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/breakpoint-mcp