figma_server_info

THE RISK

Low Risk

Why figma_server_info needs a policy

This is a diagnostic/status query operation that returns read-only information about server state and configuration. It has no capability to modify data, execute commands, or trigger external actions. The blast radius of misuse is minimal—an AI could learn technical details about the server but cannot perform destructive or financial operations.

From the tool's definition Tool description states it 'Get information about the MCP server' — retrieves metadata about package version, WebSocket port, connection state, and document info with no modification or side effects.

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

POLICY

How to control figma_server_info

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

policy.json

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

figma_server_info 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 MCP 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 MCP Bridge tools

Destructive figma_delete_mode Delete a mode from a variable collection. Cannot delete the last mode. Destructive figma_delete_nodes Delete nodes. Destructive figma_delete_page Delete a page from the Figma document. Cannot delete the last remaining page. Destructive figma_delete_variable_collection Delete a variable collection and all its variables. Use with caution - this cannot be undo Destructive figma_delete_variables Delete one or more variables from the document. Use with caution - this cannot be undone. Destructive figma_remove_reaction Prototype: remove a reaction from a node by its zero-based index in the reactions array. U Destructive figma_remove_table_column FigJam: remove the column at the given index. Destructive figma_remove_table_row FigJam: remove the row at the given index.

All 88 Figma MCP 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 figma_server_info

What does the figma_server_info tool do? +

Get information about the MCP server: package version, WebSocket port, connection state, and connected document info. It is categorised as a Read tool in the Figma MCP Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on figma_server_info? +

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

What risk level is figma_server_info? +

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

Can I rate-limit figma_server_info? +

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

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

figma_server_info is provided by the Figma MCP Bridge MCP server (magic-spells/figma-mcp-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 MCP Bridge tool call.

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

CHECK YOUR STACK →