AI agents use figma_post_comment to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
x | number | — | Canvas X coordinate to pin the comment |
y | number | — | Canvas Y coordinate to pin the comment |
message | string | Yes | |
file_key | string | Yes | |
personal_access_token | string | Yes |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by adding comments to Figma files. While non-destructive and not a direct code execution, it modifies shared design collaboration artifacts. The severity is medium because misuse could result in spam, misinformation, or disruption in collaborative design workflows, but comments are easily deletable and don't cause permanent damage to design assets themselves.
From the tool's definition Tool name 'figma_post_comment' and description 'Add a comment to a Figma file' indicates creation of new content (a comment) in a collaborative design system.
Attacks that exploit this kind of access
Add a comment to a Figma file, optionally pinned to canvas coordinates. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
figma_post_comment accepts 5 parameters: x, y, message, file_key, personal_access_token. Required: message, file_key, personal_access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for figma_post_comment: 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 UnClick. Nothing to install.
figma_post_comment 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 figma_post_comment 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 figma_post_comment. 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.
figma_post_comment is provided by the UnClick MCP server (@unclick/mcp-server). 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 →