New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cs_dbg_watch

Manage a persistent set of C# watch expressions and evaluate them in the current stopped frame. Pass add/remove/clear to mutate the set (all optional), then every current watch is re-evaluated and returned. Call with no mutation args to just re-read the watches after a step/continue. Expressions ...

SERVERBreakpoint SOURCEbreakpoint-mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/cs-dbg-watch.md

What cs_dbg_watch does on Breakpoint

AI agents call cs_dbg_watch to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
add array Expressions to add to the watch set
clear boolean Clear all watches before applying add (default false)
remove array Expressions to remove from the watch set
frame_id integer Frame id from cs_dbg_stack_trace; omit for the top frame

Parameters from the server's own tool schema.

Why cs_dbg_watch is rated Low

Although the tool has mutation operations (`add`/`remove`/`clear`), these mutate only the local watch expression set, not the debugged program's state. The core function is evaluation/inspection of variables at a breakpoint, which is a read operation. The explicit note that expressions are 'intended to be side-effect-free' in DAP watch context confirms this is fundamentally a debugging inspection tool.

From the tool's definition Tool description states it 'Manage a persistent set of C# watch expressions and evaluate them in the current stopped frame' and 'Expressions are evaluated in DAP `watch` context (intended to be side-effect-free)'.

Risk signalsBulk/mass operation — affects multiple targets

Questions about cs_dbg_watch

What does the cs_dbg_watch tool do? +

Manage a persistent set of C# watch expressions and evaluate them in the current stopped frame. Pass add/remove/clear to mutate the set (all optional), then every current watch is re-evaluated and returned. Call with no mutation args to just re-read the watches after a step/continue. Expressions are evaluated in DAP watch context (intended to be side-effect-free), so this is not gated; the results are only meaningful while the program is stopped at a breakpoint. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

What parameters does cs_dbg_watch accept? +

cs_dbg_watch accepts 4 parameters: add, clear, remove, frame_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cs_dbg_watch? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for cs_dbg_watch: 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.

What risk level is cs_dbg_watch? +

cs_dbg_watch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cs_dbg_watch? +

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

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

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

Across the catalogue

// 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 Breakpoint'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.