Add a comment to a Figma file
AI agents use figma_post_comment to create or update resources in Figma MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileKey | string | — | The file key to use for the operation |
message | string | — | The text contents of the comment to post |
comment_id | string | — | The ID of the comment to reply to, if any |
client_meta | object | — | The position where to place the comment |
Parameters from the server's own tool schema.
Posting a comment creates new data within Figma but does not modify existing design content, delete anything, execute code, or impact financial systems. This is a straightforward write operation with minimal blast radius—comments are collaboration artifacts easily removed. Severity is low because comments do not affect core design assets or team permissions.
From the tool's definition Tool name 'figma_post_comment' and description 'Add a comment to a Figma file' indicate creation of new data (comment). The action is reversible via deletion (evidenced by sibling tool 'figma_delete_comment').
Attacks that exploit this kind of access
Add a comment to a Figma file. It is categorised as a Write tool in the Figma MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
figma_post_comment accepts 4 parameters: fileKey, message, comment_id, client_meta. The full parameter table on this page comes from the server's own tool schema.
Register the Figma MCP Server 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 Figma MCP Server. 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 Figma MCP Server MCP server (thirdstrandstudio/mcp-figma). 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 →