load_font_async

THE RISK

High Risk

Why load_font_async needs a policy

Loading a font triggers an external operation (fetching and loading font resources into Figma's runtime environment) rather than simply reading or writing structured data. It involves executing an asynchronous action with side effects on the Figma environment state. Severity is low as the blast radius is minimal — misuse could result in unintended fonts being loaded but no data loss or financial impact.

From the tool's definition Load a font asynchronously in Figma

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

POLICY

How to control load_font_async

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "load_font_async": {
      "limits": [
        {
          "counter": "load_font_async_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

load_font_async stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Talk to Figma MCP tools

Destructive delete_node Delete a node from Figma Destructive delete_page Delete a page from the current Figma document Write apply_image_transform Adjust image position, scale, and rotation within node. Rotates the IMAGE inside the node, Write apply_variable_to_node Bind a variable to a node property in Figma. Call once per field — for multiple fields, ca Write boolean_operation Perform a boolean operation (union, subtract, intersect, exclude) on two or more nodes. Al Write clone_node Clone an existing node in Figma Write convert_to_frame Convert a group or shape node into a frame in Figma. Preserves position, size, visual prop Write create_component_from_node Convert an existing node (frame, group, etc.) into a reusable component in Figma

All 93 Claude Talk to Figma MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Claude Talk to Figma MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about load_font_async

What does the load_font_async tool do? +

Load a font asynchronously in Figma. It is categorised as a Execute tool in the Claude Talk to Figma MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on load_font_async? +

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

What risk level is load_font_async? +

load_font_async is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit load_font_async? +

Yes. Add a rate_limit block to the load_font_async 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 load_font_async completely? +

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

load_font_async is provided by the Claude Talk to Figma MCP server (arinspunk/claude-talk-to-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 Claude Talk to Figma MCP tool call.

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

CHECK YOUR STACK →