interact_make_draggable
Wire an existing node for drag-and-drop by attaching a generated reusable drag script (and, for node2d, a drag input action + a hit-area input_event connection). COMPOSES with the node's existing script: if it already has one, the drag script extends it, so an authored card keeps its set_data/set...
This record as markdown: /tools/breakpoint-mcp/interact-make-draggable.md
What interact_make_draggable does on Breakpoint
AI agents use interact_make_draggable 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 |
|---|---|---|---|
mode | string | Yes | control→Control _get_drag_data DnD; node2d→Area2D hit region + pointer handler |
node | string | Yes | Node path (in the open scene) to make draggable; "." for the root |
action | string | — | node2d mode: input action name registered for the drag button (default "drag") |
button | integer | — | node2d mode: mouse button index that begins the drag (default 1 = left) |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
payload | object | — | Neutral data the drag carries (bound into the script as a Dictionary); default empty |
preview | boolean | — | control mode: show a translucent drag preview (default false) |
hit_area | string | — | node2d mode: sub-path to the Area2D whose input_event drives the drag (default the node itself) |
script_path | string | Yes | Where to save the generated drag script, e.g. res://ui/interact/Draggable.gd |
Parameters from the server's own tool schema.
Why interact_make_draggable is rated Medium
This tool modifies an existing node by attaching or composing a new script to enable drag-and-drop functionality. It creates/modifies scripts attached to nodes in a reversible way (scripts can be removed/changed), making it a Write operation. It does not delete data, execute arbitrary code, or involve financial transactions.
From the tool's definition Wire an existing node for drag-and-drop by attaching a generated reusable drag script... COMPOSES with the node's existing script: if it already has one, the drag script `extends` it... never overwritten
Risk signalsAccepts raw HTML/template content (payload)
Attacks that exploit this kind of access
The rule that runs interact_make_draggable 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 interact_make_draggable, this is the rule to start with:
interact_make_draggable 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 interact_make_draggable call is checked against it from then on.
Questions about interact_make_draggable
Wire an existing node for drag-and-drop by attaching a generated reusable drag script (and, for node2d, a drag input action + a hit-area input_event connection). COMPOSES with the node's existing script: if it already has one, the drag script extends it, so an authored card keeps its set_data/set_face and merely gains drag (never overwritten). control mode uses Godot's built-in Control drag-and-drop (_get_drag_data hands off {payload, source}, with an optional translucent preview); node2d mode carries the payload and follows the pointer from a button-driven handler. General-purpose — the drag carries a caller-supplied neutral payload Dictionary, written as a per-node @export so one script serves many draggables. Decomposes onto node.get_property → resource.create → node.set_property (script + payload) (+ inputmap.add_action / add_event / signal.connect for node2d). DESTRUCTIVE (writes a script) — gated by confirmation. 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.
interact_make_draggable accepts 9 parameters: mode, node, action, button, confirm, payload, preview, hit_area, script_path. Required: mode, node, script_path. 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 interact_make_draggable: 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.
interact_make_draggable 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 interact_make_draggable 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 interact_make_draggable. 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.
interact_make_draggable 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