This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/figma-get-comments.md
What figma_get_comments does on UnClick
AI agents call figma_get_comments to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_key | string | Yes | |
personal_access_token | string | — |
Parameters from the server's own tool schema.
Why figma_get_comments is rated Low
This tool retrieves existing comment data from a Figma file without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact, as comments are typically non-sensitive collaboration artifacts. Severity is low because disclosure of comments poses minimal risk to users or systems.
From the tool's definition Tool name is 'figma_get_comments' and description states 'Get all comments on a Figma file' — the verb 'Get' explicitly indicates retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs figma_get_comments 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_get_comments, this is the rule to start with:
figma_get_comments is read-only, so it stays allowed. 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_get_comments call is checked against it from then on.
Questions about figma_get_comments
Get all comments on a Figma file. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
figma_get_comments accepts 2 parameters: file_key, personal_access_token. Required: 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_get_comments: 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_get_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the figma_get_comments 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_get_comments. 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_get_comments 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