figma_post_comment
Add a comment to a Figma file, optionally pinned to canvas coordinates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/figma-post-comment.md
What figma_post_comment does on UnClick
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 | — |
Parameters from the server's own tool schema.
Why figma_post_comment is rated Medium
An AI agent can call figma_post_comment faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs figma_post_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For figma_post_comment, this is the rule to start with:
figma_post_comment 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 UnClick, apply this rule, and every figma_post_comment call is checked against it from then on.
Questions about figma_post_comment
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. 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue