Figma (Framelink)

The material explicitly states there are no required keys or environment variables. No API token, account credential, or other sensitive secret is requested, so credential exposure and abuse risk appears low.

The material declares no remote host endpoints and does not describe sending user data to any third-party service. Based on the available facts, there is no clear network egress path or unknown external recipient.

The system flags that this tool executes code; as an MCP tool, that typically means spawning a local process and handling inputs. This is a normal capability for such tools, but you should still review what system commands it can invoke and under what privileges.

The description says it 'reads Figma design data and turns designs into code,' indicating it accesses design-related content at minimum. The current material does not specify the exact read/write scope or whether local files/project directories are involved, so it should be treated with normal caution for access to design data.

Supply-chain trust signals are strong: it is open source, platform-curated, has about 15k stars, and is marked as an official source, which improves auditability and lowers risk. However, the missing README, undeclared license, and unknown maintenance status leave transparency gaps, so a caution rating is more appropriate than high risk.