node_remove_from_group
Remove a node from a group (undoable). No-op if not a member.
This record as markdown: /tools/breakpoint-mcp/node-remove-from-group.md
What node_remove_from_group does on Breakpoint
AI agents use node_remove_from_group 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 |
group | string | Yes | Group name |
Parameters from the server's own tool schema.
Why node_remove_from_group is rated Medium
The tool modifies group membership by removing a node, but is explicitly stated to be undoable, making it reversible. This fits the Write category. Severity is medium as misuse could disrupt scene organization but can be reversed.
From the tool's definition Remove a node from a group (undoable). No-op if not a member.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_remove_from_group 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 node_remove_from_group, this is the rule to start with:
node_remove_from_group 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 node_remove_from_group call is checked against it from then on.
Questions about node_remove_from_group
Remove a node from a group (undoable). No-op if not a member. 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.
node_remove_from_group accepts 2 parameters: path, group. Required: path, group. 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 node_remove_from_group: 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.
node_remove_from_group 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 node_remove_from_group 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 node_remove_from_group. 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.
node_remove_from_group 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