dbg_variables
List variables under a scope or a complex value (via its variables_ref). Requires a stop (not_stopped) — a reference is only valid within the stop that issued it.
This record as markdown: /tools/breakpoint-mcp/dbg-variables.md
What dbg_variables does on Breakpoint
AI agents call dbg_variables 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
variables_ref | integer | Yes | variablesReference from dbg_scopes or a parent variable |
Parameters from the server's own tool schema.
Why dbg_variables is rated Low
Even though dbg_variables only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs dbg_variables 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_variables, this is the rule to start with:
dbg_variables is read-only, so it stays allowed. 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_variables call is checked against it from then on.
Questions about dbg_variables
List variables under a scope or a complex value (via its variables_ref). Requires a stop (not_stopped) — a reference is only valid within the stop that issued it. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
dbg_variables accepts 1 parameter: variables_ref. Required: 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_variables: 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_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dbg_variables 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_variables. 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_variables 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