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

cs_dbg_restart

Restart the current C# debug session. Uses the DAP restart request when the adapter advertises supportsRestartRequest, otherwise falls back to terminate + relaunch — so it works on every adapter (netcoredbg advertises none, so the relaunch path runs). Reuses the last cs_dbg_launch/cs_dbg_attach p...

SERVERBreakpoint SOURCEbreakpoint-mcp
High RISK CLASS
Category Execute
Parameters 30 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What cs_dbg_restart does on Breakpoint

AI agents invoke cs_dbg_restart 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.

ParameterTypeRequiredDescription
args array Override the program arguments (launched sessions)
program string Override the launched program (launched sessions)
stop_on_entry boolean Override stop-at-entry for the restart (launched sessions)

Parameters from the server's own tool schema.

Why cs_dbg_restart is rated High

This tool executes a debugger restart operation, which is a control-flow action that can alter program execution state. While not destructive (the operation is reversible), it clearly triggers external operations (restarting a debug session, relaunching a program) that fall under the Execute category.

From the tool's definition Tool description explicitly states it "Restart[s] the current C# debug session" and performs a DAP `restart` request or `terminate + relaunch`.

Risk signalsBulk/mass operation — affects multiple targets

Questions about cs_dbg_restart

What does the cs_dbg_restart tool do? +

Restart the current C# debug session. Uses the DAP restart request when the adapter advertises supportsRestartRequest, otherwise falls back to terminate + relaunch — so it works on every adapter (netcoredbg advertises none, so the relaunch path runs). Reuses the last cs_dbg_launch/cs_dbg_attach parameters; pass stop_on_entry / program / args to override them for a launched session. method in the result reports which path ran ('restart' = native DAP restart, 'relaunch' = terminate + fresh handshake). Requires a session started with cs_dbg_launch/cs_dbg_attach. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does cs_dbg_restart accept? +

cs_dbg_restart accepts 3 parameters: args, program, stop_on_entry. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cs_dbg_restart? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for cs_dbg_restart: 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_restart? +

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

Can I rate-limit cs_dbg_restart? +

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

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

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

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