mp_add_synchronizer
Add a MultiplayerSynchronizer node under a parent (undoable) and, if properties are given, build a SceneReplicationConfig that replicates them. root_path is the node the property NodePaths are relative to (default "..", the synchronizer's parent). Property paths look like ".:position" or "Sprite2...
This record as markdown: /tools/breakpoint-mcp/mp-add-synchronizer.md
What mp_add_synchronizer does on Breakpoint
AI agents use mp_add_synchronizer 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 |
|---|---|---|---|
name | string | — | Node name (default MultiplayerSynchronizer) |
root_path | string | — | NodePath the replicated property paths are relative to (default "..") |
properties | array | — | Property NodePaths to replicate, e.g. [".:position", ".:rotation"] |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
replication_mode | string | — | Replication mode for the properties (default always) |
Parameters from the server's own tool schema.
Why mp_add_synchronizer is rated Medium
This tool creates and modifies scene nodes and replication configuration in what appears to be a game engine (likely Godot based on the node/scene terminology). It does not execute external commands, run arbitrary code, or delete data irreversibly. The 'undoable' designation confirms reversibility.
From the tool's definition Tool description states it can 'Add a MultiplayerSynchronizer node under a parent (undoable)' and 'build a SceneReplicationConfig that replicates them.' The term 'undoable' indicates reversible modification of scene structure and configuration.
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 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 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 SceneReplicationConfig that replicates them. root_path is the node the property NodePaths are relative to (default "..", the synchronizer's parent). Property paths look like ".:position" or "Sprite2D:rotation". Pure node authoring — no service is started. 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.
mp_add_synchronizer accepts 5 parameters: name, root_path, properties, parent_path, replication_mode. Required: parent_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 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 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 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