New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERBreakpoint SOURCEbreakpoint-mcp
Medium RISK CLASS
Category Write
Parameters 51 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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

Questions about mp_add_synchronizer

What does the mp_add_synchronizer tool do? +

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.

What parameters does mp_add_synchronizer accept? +

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.

How do I enforce a policy on mp_add_synchronizer? +

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.

What risk level is mp_add_synchronizer? +

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

Can I rate-limit mp_add_synchronizer? +

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.

How do I block mp_add_synchronizer completely? +

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.

What MCP server provides mp_add_synchronizer? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Breakpoint's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.