Set primary and counter axis alignment for an auto-layout frame in Figma
AI agents use set_axis_align to create or update resources in Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Talk to Figma MCP environment.
set_axis_align modifies existing frame layout properties reversibly. It is a Write operation (update) rather than Destructive (no deletion), Execute (no arbitrary code), or Read (has side effects). Severity is medium because misalignment could break a design's intended layout, requiring manual correction, but the change is reversible and doesn't destroy data or move money.
From the tool's definition Tool modifies frame alignment properties in Figma ('Set primary and counter axis alignment for an auto-layout frame'). This changes design layout without deleting or creating new elements.
Attacks that exploit this kind of access
Set primary and counter axis alignment for an auto-layout frame in Figma. It is categorised as a Write tool in the Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Talk to Figma MCP server in PolicyLayer and add a rule for set_axis_align: 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 Talk to Figma MCP. Nothing to install.
set_axis_align 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 set_axis_align 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 set_axis_align. 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.
set_axis_align is provided by the Talk to Figma MCP server (pipethedev/talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →