add_comment
AI agents use add_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.
Adding comments to Figma files creates new data that persists in the design document. This is reversible (comments can be deleted) and has no financial impact, making it Write rather than Execute or Destructive. Severity is medium because comment spam or malicious comments could disrupt collaborative workflows and project data integrity, though the blast radius is limited to the specific Figma file.
From the tool's definition Tool name 'add_comment' indicates data modification capability. Sibling tools show this server creates and modifies Figma design objects (create_frame_in_figma, create_rectangle, etc.). Adding comments creates new data in Figma projects.
Attacks that exploit this kind of access
add_comment. 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.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_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 add_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 add_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.
add_comment is provided by the Figma MCP Server MCP server (sichang824/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 →