selection_set
Replace the editor's node selection with the given node paths.
This record as markdown: /tools/breakpoint-mcp/selection-set.md
What selection_set does on Breakpoint
AI agents use selection_set 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 |
|---|---|---|---|
paths | array | Yes | Node paths relative to the scene root |
Parameters from the server's own tool schema.
Why selection_set is rated Medium
This tool modifies editor state by replacing the current selection, which is a reversible change (the user can select different nodes afterward). It does not execute arbitrary code, delete data permanently, or affect financial systems.
From the tool's definition Tool description states "Replace the editor's node selection with the given node paths" — the verb "Replace" indicates a modification operation that changes editor state.
Attacks that exploit this kind of access
The rule that runs selection_set 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 selection_set, this is the rule to start with:
selection_set 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 selection_set call is checked against it from then on.
Questions about selection_set
Replace the editor's node selection with the given node paths. 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.
selection_set accepts 1 parameter: paths. Required: paths. 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 selection_set: 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.
selection_set 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 selection_set 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 selection_set. 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.
selection_set 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