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...
This record as markdown: /tools/breakpoint-mcp/cs-dbg-set-exception-breakpoints.md
What cs_dbg_set_exception_breakpoints does on Breakpoint
AI agents use cs_dbg_set_exception_breakpoints to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
filters | array | — | 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.
Why cs_dbg_set_exception_breakpoints is rated Medium
An AI agent can call cs_dbg_set_exception_breakpoints faster than any human can review: one bad instruction and it creates or modifies resources in Breakpoint by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs cs_dbg_set_exception_breakpoints safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cs_dbg_set_exception_breakpoints, this is the rule to start with:
cs_dbg_set_exception_breakpoints stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every cs_dbg_set_exception_breakpoints call is checked against it from then on.
Questions about 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). A filter id the adapter does not advertise is refused by name, listing the real ones, rather than forwarded to the adapter as an opaque failure. 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. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
cs_dbg_set_exception_breakpoints accepts 1 parameter: filters. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for cs_dbg_set_exception_breakpoints: 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 Breakpoint. Nothing to install.
cs_dbg_set_exception_breakpoints is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cs_dbg_set_exception_breakpoints 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 cs_dbg_set_exception_breakpoints. 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.
cs_dbg_set_exception_breakpoints is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue