Low Risk

get_component_properties

Get all component properties and their current values from a component instance

How to control get_component_properties ↓

What get_component_properties does on Figma AI Bridge

AI agents call get_component_properties to retrieve information from Figma AI Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_component_properties needs a policy

This tool queries and retrieves existing component property data from Figma. It performs a read-only operation that does not create, modify, delete, or execute any actions. The word 'Get' combined with 'current values' confirms data retrieval only. No design elements are altered, no external operations are triggered, and no financial implications exist.

From the tool's definition Tool name 'get_component_properties' and description 'Get all component properties and their current values from a component instance' indicate a retrieval operation with no modification or side effects.

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

How to control get_component_properties

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_component_properties:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_component_properties": {}
  }
}

get_component_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Figma AI Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_component_properties

What does the get_component_properties tool do? +

Get all component properties and their current values from a component instance. 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_component_properties? +

Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for get_component_properties: 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_component_properties? +

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

Can I rate-limit get_component_properties? +

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

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

get_component_properties 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.

Free to start. No card required.

64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.