Sap Breakpoint Set
sap_breakpoint_setSets an external ABAP breakpoint at a specified line or source match for SAP GUI debugging; requires explicit human approval because the session halts in the ABAP debugger.
Instructions
HIGHLY DANGEROUS — DO NOT CALL unless a human user has explicitly asked for a breakpoint to be set. Live-verified (issue #791): once the breakpoint fires, the SAP session stops and SAP GUI opens the ABAP debugger. The call that triggered it and every later call on that session fail after a few seconds with an error naming the debugger, as can slow calls on other sessions of the same SAP connection; sessions of other connections are not affected. The session works again once a human continues or exits the debugger in SAP GUI.
Set an external ABAP breakpoint on a specific line of a program, class method, or function module. Desktop backend only — WebGUI does not support external breakpoints.
Provide either line_number (1-indexed SAP display line) or match_pattern (substring or regex matched against source lines).
SAP toggles breakpoints: if the line already has a breakpoint, VKey 45 deletes it. This tool only sets the breakpoint — it does not run anything.
IMPORTANT — before calling this tool, ask the human operator for explicit permission and explain the consequences: there is NO tool to step, continue, or read variables in the resulting debugger. If the breakpoint later fires during a GUI run, SAP GUI opens a modal interactive ABAP debugger that only a human can drive — the agent cannot see or control it, and it may fire once per row/iteration if the code path repeats. The halted session is unusable for the agent until then, as described above. Only proceed once the human has confirmed they intend to sit at the SAP GUI and step through the debugger themselves; do not use this to silently 'verify a code path is reached' from an unattended flow.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"object_type": "<object_type>",
"object_name": "<object_name>"
},
"name": "sap_breakpoint_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session | No | Session ID (e.g., "s1"). None uses primary session. | |
| agent_id | No | Agent identifier for binding check. Optional. | |
| line_number | No | 1-indexed SAP display line. Mutually exclusive with match_pattern. | |
| method_name | No | Required for CLAS (method name) and FUGR (function module name). | |
| object_name | Yes | Program name, class name, or function group name. | |
| object_type | Yes | "PROG" for programs, "CLAS" for classes, "FUGR" for function groups. | |
| match_pattern | No | Substring or regex matched against source. Mutually exclusive with line_number. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | Error message if success=False | |
| popup | No | Present when a popup dialog is active on screen | |
| action | No | What actually happened | set |
| success | No | Whether the operation succeeded | |
| line_number | No | Resolved 1-indexed line number | |
| method_name | No | Method or function module name (None for PROG) | |
| object_name | Yes | Program name, class name, or function group name | |
| object_type | Yes | Object type: PROG, CLAS, or FUGR | |
| active_window | No | Which window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open. | |
| status_message | No | Raw SAP status bar message | |
| confirmation_skipped | No | True if the breakpoint was armed without a real human confirmation (the connected MCP client doesn't support elicitation, or asking failed) — fail-open. False means a human explicitly confirmed via the client's confirmation dialog. |