set_api_key

Set your Figma API personal access token (will be saved to ~/.mcp-figma/config.json)

Handles credentials or secrets (api_key)

Part of the Figma API Integration MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use set_api_key to create or modify resources in Figma API Integration. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON SET_API_KEY

Without a policy, an AI agent could call set_api_key repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Figma API Integration.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

ai-zerolab-mcp-figma.yaml

tools:
  set_api_key:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Figma API Integration policy for all 18 tools.

// DETAILS

Tool Name set_api_key

Category Write

MCP Server Figma API Integration MCP Server

Risk Level Medium

// MORE FIGMA API INTEGRATION TOOLS

Destructive delete_comment Write post_comment Read check_api_key Read get_comments Read get_component Read get_file Read get_file_components Read get_file_nodes

View all 18 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like set_api_key have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the set_api_key tool do? +

Set your Figma API personal access token (will be saved to ~/.mcp-figma/config.json). It is categorised as a Write tool in the Figma API Integration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_api_key? +

Add a rule in your Intercept YAML policy under the tools section for set_api_key. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Figma API Integration MCP server.

What risk level is set_api_key? +

set_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_api_key? +

Yes. Add a rate_limit block to the set_api_key rule in your Intercept 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 set_api_key completely? +

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

set_api_key is provided by the Figma API Integration MCP server (ai-zerolab/mcp-figma). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

set_api_key

Let agents act without letting them run wild.