figma_list_projects

List all projects for a Figma team.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/figma-list-projects.md

WHAT IT DOES

What figma_list_projects does on Integrations MCP

AI agents call figma_list_projects to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why figma_list_projects is rated Low

This is a read-only query operation that retrieves information about existing Figma projects. It has no side effects, does not modify data, and poses minimal risk even if misused by an AI agent — the worst outcome is unauthorized visibility into project names and metadata that may already be accessible to the authenticated user.

From the tool's definition Tool name and description indicate 'list' operation: 'List all projects for a Figma team' — retrieves project metadata without modifying or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs figma_list_projects safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For figma_list_projects, this is the rule to start with:

figma_list_projects Allowed

figma_list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every figma_list_projects call is checked against it from then on.

FAQ

Questions about figma_list_projects

What does the figma_list_projects tool do? +

List all projects for a Figma team. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on figma_list_projects? +

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

What risk level is figma_list_projects? +

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

Can I rate-limit figma_list_projects? +

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

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

figma_list_projects is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →