List all pages in the current Figma document. Returns page IDs, names, and indicates which page is currently active.
AI agents call figma_list_pages to retrieve information from Figma MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
figma_list_pages only queries and returns information about pages (IDs, names, and active status) without modifying, creating, deleting, or executing any operations. It fits the Read category as a straightforward data retrieval tool with minimal security risk.
From the tool's definition Tool description states 'List all pages in the current Figma document. Returns page IDs, names, and indicates which page is currently active.' This is a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access figma_list_pages gives an agent:
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_list_pages:
{
"version": "1",
"default": "deny",
"tools": {
"figma_list_pages": {}
}
} figma_list_pages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all pages in the current Figma document. Returns page IDs, names, and indicates which page is currently active. It is categorised as a Read tool in the Figma MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP Bridge MCP server in PolicyLayer and add a rule for figma_list_pages: 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.
figma_list_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the figma_list_pages 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.
Set action: deny in the PolicyLayer policy for figma_list_pages. 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.
figma_list_pages 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.
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.
Free to start. No card required.
88 Figma MCP Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.