control_set_size_flags
Set a Control's container size flags and/or stretch ratio (undoable). 'horizontal'/'vertical' are SizeFlags bitmasks (1=fill, 2=expand, 3=expand_fill, 4=shrink_center, 8=shrink_end). Provide at least one of horizontal/vertical/stretch_ratio.
This record as markdown: /tools/breakpoint-mcp/control-set-size-flags.md
What control_set_size_flags does on Breakpoint
AI agents use control_set_size_flags 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 | Control node path relative to the scene root |
vertical | integer | — | size_flags_vertical bitmask |
horizontal | integer | — | size_flags_horizontal bitmask |
stretch_ratio | number | — | size_flags_stretch_ratio (default 1.0) |
Parameters from the server's own tool schema.
Why control_set_size_flags is rated Medium
This tool modifies GUI layout properties (size flags and stretch ratio) of a UI Control element. It is reversible (marked 'undoable'), making it a Write operation rather than Execute or Destructive. The severity is medium because misuse could alter UI layouts in unintended ways, but the blast radius is limited to visual layout changes without data loss or command execution.
From the tool's definition The tool 'Set a Control's container size flags and/or stretch ratio (undoable)' modifies UI control properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs control_set_size_flags 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_size_flags, this is the rule to start with:
control_set_size_flags 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_size_flags call is checked against it from then on.
Questions about control_set_size_flags
Set a Control's container size flags and/or stretch ratio (undoable). 'horizontal'/'vertical' are SizeFlags bitmasks (1=fill, 2=expand, 3=expand_fill, 4=shrink_center, 8=shrink_end). Provide at least one of horizontal/vertical/stretch_ratio. 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_size_flags accepts 4 parameters: path, vertical, horizontal, stretch_ratio. 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_size_flags: 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_size_flags 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_size_flags 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_size_flags. 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_size_flags 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