control_set_anchors
Set one or more of a Control's anchors (left/top/right/bottom, each 0..1) directly (undoable). Only the sides you pass are changed; offsets are left as-is. Provide at least one side.
This record as markdown: /tools/breakpoint-mcp/control-set-anchors.md
What control_set_anchors does on Breakpoint
AI agents use control_set_anchors 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 |
|---|---|---|---|
top | number | — | anchor_top (0..1) |
left | number | — | anchor_left (0..1) |
path | string | Yes | Control node path relative to the scene root |
right | number | — | anchor_right (0..1) |
bottom | number | — | anchor_bottom (0..1) |
Parameters from the server's own tool schema.
Why control_set_anchors is rated Medium
This tool creates or modifies data (Control anchor values) in a reversible manner. The "undoable" designation confirms the change can be reverted. While it affects UI layout, it does not execute arbitrary code, delete data, or cause financial harm. This is a straightforward Write operation with medium severity due to potential for misalignment of UI elements if misused by an agent.
From the tool's definition Tool description states it "Set[s] one or more of a Control's anchors" and is marked "(undoable)", indicating reversible modification of UI control properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs control_set_anchors 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 control_set_anchors, this is the rule to start with:
control_set_anchors 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 control_set_anchors call is checked against it from then on.
Questions about control_set_anchors
Set one or more of a Control's anchors (left/top/right/bottom, each 0..1) directly (undoable). Only the sides you pass are changed; offsets are left as-is. Provide at least one side. 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.
control_set_anchors accepts 5 parameters: top, left, path, right, bottom. Required: 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 control_set_anchors: 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.
control_set_anchors 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 control_set_anchors 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 control_set_anchors. 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.
control_set_anchors 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