High-risk tools in Godot Breakpoint

High severity Godot Breakpoint MCP Server 27 of 239 tools

27 of the 239 tools in Godot Breakpoint are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.

Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.

Tools at high risk

cs_dbg_attach Execute

Attach netcoredbg to an already-running .NET process (e.g. a C# Godot game launched separately) by its OS process id.
cs_dbg_continue Execute

Resume execution and wait for the program to settle again (next breakpoint or termination).
cs_dbg_evaluate Execute

Evaluate a C# expression in the context of a stopped frame. DESTRUCTIVE: arbitrary code execution — confirm with the user and keep this gated.
cs_dbg_launch Execute

Start a C# Godot game under netcoredbg.
cs_dbg_restart Execute

Restart the current C# debug session. Uses the DAP
cs_dbg_set_exception_breakpoints Execute

Enable (replace) the debugger
cs_dbg_step Execute

Step execution:
dbg_attach Execute

Attach to an already-running Godot debug session.
dbg_continue Execute

Resume execution and wait for the program to settle again (next breakpoint or termination).
dbg_evaluate Execute

Evaluate a GDScript expression in the context of a stopped frame. DESTRUCTIVE: arbitrary code execution — confirm with the user and keep this capability gated.
dbg_goto Execute

Move the program counter within the current stopped frame —
dbg_launch Execute

Start the game under the debugger. scene may be
dbg_restart Execute

Restart the current debug session. Uses the DAP
dbg_set_exception_breakpoints Execute

Enable (replace) the debugger
dbg_set_variable Execute

Change a variable
dbg_step Execute

Step execution:
filesystem_scan Execute

Trigger an editor rescan of the project filesystem so newly added or externally-changed files are picked up. Read-only side effect.
godot_launch_editor Execute

Open the Godot editor for the configured project (detached). Needed before any editor_* bridge tool can be used.
godot_run_managed Execute

Run the project as a managed child process with captured stdout/stderr, so godot_output can read ALL print()/error output.
godot_run_project Execute

Run the project (detached). Optionally start from a specific scene path (res://...). Returns the process id.
godot_stop Execute

Terminate a managed process started by godot_run_managed.
node_call_method Execute

Invoke a method on a node in the EDITED scene. DESTRUCTIVE (arbitrary invocation, not undoable) — gated by confirmation.
runtime_call_method Execute

Invoke a method on a live node. DESTRUCTIVE (arbitrary invocation) — gated by confirmation. Args use the tagged-Variant convention.
runtime_emit_signal Execute

Emit a signal from a live node. DESTRUCTIVE — gated by confirmation.
runtime_inject_input Execute

Inject a synthetic input event for automated play-testing. DESTRUCTIVE.
runtime_set_property Execute

Set a property on a live node. DESTRUCTIVE (mutates running game state) — gated by confirmation. Rich types use the {\
signal_emit Execute

Emit a signal from a node in the EDITED scene, firing its connected callables now. DESTRUCTIVE (edit-time side effects) — gated by confirmation. Args use the tagged-Variant conv...

Attacks that target this class

High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.

High-risk tools in Godot Breakpoint

Tools at high risk

Attacks that target this class

More on Godot Breakpoint

Enforce policy on every Godot Breakpoint tool call.