mp_add_synchronizer
Add a MultiplayerSynchronizer node under a parent (undoable) and, if properties are given, build a
This record as markdown: /tools/godot-breakpoint-mcp/mp-add-synchronizer.md
What mp_add_synchronizer does on Godot Breakpoint
AI agents use mp_add_synchronizer to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why mp_add_synchronizer is rated Medium
This tool creates a new multiplayer synchronizer node in the Godot editor, which modifies the scene tree. The reversibility via undo means it is not destructive. While it affects game state configuration, the blast radius is limited to the current project/scene being edited. Categorized as Write (creates/adds data reversibly) with medium severity due to potential unintended scene modifications if misused by an agent.
From the tool's definition Tool name contains 'add' and description states 'Add a MultiplayerSynchronizer node under a parent'. The '(undoable)' note indicates the action is reversible through undo functionality, confirming this is a write operation rather than destructive.
Attacks that exploit this kind of access
The rule that runs mp_add_synchronizer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mp_add_synchronizer, this is the rule to start with:
mp_add_synchronizer 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 Godot Breakpoint, apply this rule, and every mp_add_synchronizer call is checked against it from then on.
Questions about mp_add_synchronizer
Add a MultiplayerSynchronizer node under a parent (undoable) and, if properties are given, build a. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for mp_add_synchronizer: 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 Godot Breakpoint. Nothing to install.
mp_add_synchronizer 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 mp_add_synchronizer 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 mp_add_synchronizer. 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.
mp_add_synchronizer is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue