cs_dbg_continue

Resume execution and wait for the program to settle again (next breakpoint or termination). Returns the resulting state; if it runs on with no further breakpoint, reports state 'running'.

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 00 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-continue.md

WHAT IT DOES

What cs_dbg_continue does on Breakpoint

AI agents use cs_dbg_continue 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.

RISK

Why cs_dbg_continue is rated Medium

An AI agent can call cs_dbg_continue 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

RECOMMENDED RULE

The rule that runs cs_dbg_continue 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_continue, this is the rule to start with:

cs_dbg_continue Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cs_dbg_continue": {
      "limits": [
        {
          "counter": "cs_dbg_continue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every cs_dbg_continue call is checked against it from then on.

FAQ

Questions about cs_dbg_continue

What does the cs_dbg_continue tool do? +

Resume execution and wait for the program to settle again (next breakpoint or termination). Returns the resulting state; if it runs on with no further breakpoint, reports state 'running'. 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.

How do I enforce a policy on cs_dbg_continue? +

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

cs_dbg_continue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cs_dbg_continue? +

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

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

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

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 280 Breakpoint tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →