interact_add_drop_zone

SERVERBreakpoint SOURCEbreakpoint-mcp

Medium RISK CLASS

Category Write

Parameters 93 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/interact-add-drop-zone.md

WHAT IT DOES

What interact_add_drop_zone does on Breakpoint

AI agents use interact_add_drop_zone 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→_can_drop_data / _drop_data overrides; node2d→Area2D hit region + try_drop() seam
`node`	string	Yes	Node path (in the open scene) to mark as a drop zone; "." for the root
`size`	object	—	node2d mode: DropArea hit size in px (default 96×96)
`shape`	string	—	node2d mode: DropArea collision shape (default rectangle)
`notify`	object	—	Optionally connect on_drop to a handler in the same call
`accepts`	object	—	Neutral accept predicate (accept-any when omitted)
`confirm`	boolean	—	Auto-approve this destructive action (skip the confirmation prompt)
`on_drop`	string	—	User signal emitted with the payload on a valid drop (default "dropped")
`script_path`	string	Yes	Where to save the generated drop-zone script, e.g. res://ui/interact/DropZone.gd

Parameters from the server's own tool schema.

RISK

Why interact_add_drop_zone is rated Medium

This tool creates or modifies scene nodes, scripts, and signal connections in what appears to be a Godot game engine context. These are reversible Write operations (nodes and connections can be removed, scripts can be detached). It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial).

From the tool's definition Tool description states it 'Attaches a generated validator/acceptor script', 'builds an Area2D + CollisionShape2D', and 'optionally connects on_drop to a handler with a persisted connection' — all are reversible modifications to scene state and script…

Risk signalsHigh parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs interact_add_drop_zone 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_add_drop_zone, this is the rule to start with:

interact_add_drop_zone Rate-limited

interact_add_drop_zone 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "interact_add_drop_zone": {
      "limits": [
        {
          "counter": "interact_add_drop_zone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every interact_add_drop_zone call is checked against it from then on.

FAQ

Questions about interact_add_drop_zone

What does the interact_add_drop_zone tool do? +

Mark a node as a drop target that validates an incoming payload and emits a signal on a valid drop. Attaches a generated validator/acceptor script that DECLARES the on_drop signal (so it survives a scene reload), and (for node2d) builds an Area2D + CollisionShape2D hit region; optionally connects on_drop to a handler with a persisted connection. accepts is the neutral predicate {key, values} — accept any payload when omitted, else accept when payload[key] is one of values. control mode overrides _can_drop_data / _drop_data; node2d exposes a try_drop(payload) seam. General-purpose — no domain vocabulary. Decomposes onto (node.add + resource.create + node.set_property for node2d) → resource.create → node.set_property (+ a persisted signal.connect). 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.

What parameters does interact_add_drop_zone accept? +

interact_add_drop_zone accepts 9 parameters: mode, node, size, shape, notify, accepts, confirm, on_drop, script_path. Required: mode, node, script_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on interact_add_drop_zone? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for interact_add_drop_zone: 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.

What risk level is interact_add_drop_zone? +

interact_add_drop_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit interact_add_drop_zone? +

Yes. Add a rate_limit block to the interact_add_drop_zone 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.

How do I block interact_add_drop_zone completely? +

Set action: deny in the PolicyLayer policy for interact_add_drop_zone. 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.

What MCP server provides interact_add_drop_zone? +

interact_add_drop_zone 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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →