dbg_set_variable
Change a variable's value in a stopped frame (DAP setVariable). DESTRUCTIVE: mutates live program state — confirm with the user and keep this gated. variables_ref is the container's variablesReference (from dbg_scopes, or a complex entry in dbg_variables), name is the variable's name within it, a...
This record as markdown: /tools/breakpoint-mcp/dbg-set-variable.md
What dbg_set_variable does on Breakpoint
AI agents use dbg_set_variable 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 |
|---|---|---|---|
name | string | Yes | Variable name within that container |
value | string | Yes | New value as a GDScript literal/expression |
confirm | boolean | — | Auto-approve this mutation (skip the confirmation prompt) |
variables_ref | integer | Yes | variablesReference of the containing scope/variable (from dbg_scopes or dbg_variables) |
Parameters from the server's own tool schema.
Why dbg_set_variable is rated Medium
An AI agent can call dbg_set_variable 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 dbg_set_variable 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 dbg_set_variable, this is the rule to start with:
dbg_set_variable 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 dbg_set_variable call is checked against it from then on.
Questions about dbg_set_variable
Change a variable's value in a stopped frame (DAP setVariable). DESTRUCTIVE: mutates live program state — confirm with the user and keep this gated. variables_ref is the container's variablesReference (from dbg_scopes, or a complex entry in dbg_variables), name is the variable's name within it, and value is the new value as a GDScript literal/expression. Only meaningful while stopped at a breakpoint. 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.
dbg_set_variable accepts 4 parameters: name, value, confirm, variables_ref. Required: name, value, variables_ref. 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 dbg_set_variable: 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.
dbg_set_variable 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 dbg_set_variable 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 dbg_set_variable. 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.
dbg_set_variable 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