get_local_components

THE RISK

Low Risk

Why get_local_components needs a policy

This tool retrieves/queries existing components from a Figma document without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if called by an AI agent, as it only exposes read-only design metadata.

From the tool's definition Tool name is 'get_local_components' and description states 'Get all local components from the Figma document' — uses the verb 'Get' indicating pure retrieval with no modification or side effects.

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

POLICY

How to control get_local_components

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

policy.json

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

get_local_components 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 AI Bridge — 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 AI Bridge tools

Destructive delete_multiple_nodes Delete multiple nodes from Figma at once Destructive delete_node Delete a node from Figma Execute set_focus Set focus on a specific node in Figma by selecting it and scrolling viewport to it Execute set_selections Set selection to multiple nodes in Figma and scroll viewport to show them Write batch_slides Create multiple presentation slides in Figma in a single batch call. Much faster than crea Write bind_variable_to_fill Bind a design token variable to a node Write bind_variable_to_stroke Bind a design token variable to a node Write clone_node Clone an existing node in Figma

All 64 Figma AI Bridge 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 get_local_components

What does the get_local_components tool do? +

Get all local components from the Figma document. It is categorised as a Read tool in the Figma AI Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_local_components? +

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

What risk level is get_local_components? +

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

Can I rate-limit get_local_components? +

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

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

get_local_components is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Figma AI Bridge tool call.

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

CHECK YOUR STACK →