mp_set_authority
Set a node's multiplayer authority (set_multiplayer_authority) to a peer id (undoable). The authority peer is the one allowed to push "authority"-mode RPCs and MultiplayerSynchronizer state for that node. peer_id 1 is the server. Pure node authoring.
This record as markdown: /tools/breakpoint-mcp/mp-set-authority.md
What mp_set_authority does on Breakpoint
AI agents use mp_set_authority 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 |
|---|---|---|---|
path | string | Yes | Node path relative to the scene root |
peer_id | integer | Yes | Peer id to grant authority (1 = server) |
recursive | boolean | — | Also apply to descendants (default true) |
Parameters from the server's own tool schema.
Why mp_set_authority is rated Medium
This tool modifies multiplayer network state by reassigning authority over a node to a different peer. While marked as undoable (reversible), it changes system configuration that affects network permissions and synchronization behavior. This makes it Write rather than Execute (no arbitrary code execution) or Destructive (reversible).
From the tool's definition Set a node's multiplayer authority...to a peer id (undoable)
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs mp_set_authority 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_set_authority, this is the rule to start with:
mp_set_authority 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_set_authority call is checked against it from then on.
Questions about mp_set_authority
Set a node's multiplayer authority (set_multiplayer_authority) to a peer id (undoable). The authority peer is the one allowed to push "authority"-mode RPCs and MultiplayerSynchronizer state for that node. peer_id 1 is the server. Pure node authoring. 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_set_authority accepts 3 parameters: path, peer_id, recursive. Required: path, peer_id. 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_set_authority: 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_set_authority 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_set_authority 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_set_authority. 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_set_authority 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