Export extracted tokens to Figma Tokens JSON.
AI agents use design_figma_export to create or update resources in SIN-Code-Frontend-Design-Skill — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SIN-Code-Frontend-Design-Skill environment.
This tool creates or modifies design token data in Figma by exporting tokens to JSON format. While the export itself is a structured output operation, the implied destination (Figma) and the fact that it writes/syncs data to an external design system classifies this as Write rather than Read.
From the tool's definition Tool name contains 'export' and description states it exports tokens to Figma JSON format, which creates or modifies data in Figma. The action is reversible (tokens can be updated or deleted in Figma afterward).
Attacks that exploit this kind of access
Export extracted tokens to Figma Tokens JSON. It is categorised as a Write tool in the SIN-Code-Frontend-Design-Skill MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SIN-Code-Frontend-Design-Skill MCP server in PolicyLayer and add a rule for design_figma_export: 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 SIN-Code-Frontend-Design-Skill. Nothing to install.
design_figma_export 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 design_figma_export 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 design_figma_export. 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.
design_figma_export is provided by the SIN-Code-Frontend-Design-Skill MCP server (opensin-code/sin-code-frontend-design-skill). 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 →