read_comments

THE RISK

Low Risk

Why read_comments needs a policy

This tool retrieves existing comments from a Figma file without modifying, deleting, or executing any operations. It is a straightforward read-only query operation that poses minimal risk to data integrity or system security.

From the tool's definition Tool name is 'read_comments' and description states 'Get all comments on a Figma file' — a pure retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access read_comments gives an agent:

POLICY

How to control read_comments

PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_comments:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_comments": {}
  }
}

read_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Figma MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma MCP Server tools

Write post_comment Post a comment on a node in a Figma file Write reply_to_comment Reply to an existing comment in a Figma file Read view_node Get a thumbnail for a specific node in a Figma file Read add_figma_file Add a Figma file to your context

All 5 Figma MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about read_comments

What does the read_comments tool do? +

Get all comments on a Figma file. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_comments? +

Register the Figma MCP Server MCP server in PolicyLayer and add a rule for read_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 Figma MCP Server. Nothing to install.

What risk level is read_comments? +

read_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_comments? +

Yes. Add a rate_limit block to the read_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.

How do I block read_comments completely? +

Set action: deny in the PolicyLayer policy for read_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.

What MCP server provides read_comments? +

read_comments is provided by the Figma MCP Server MCP server (matthewdailey/figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Figma MCP Server tool call.

Start from Figma MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →