set_current_page · Claude Talk to Figma MCP: Risk & Policy

WHAT IT DOES

What set_current_page does on Claude Talk to Figma MCP

AI agents use set_current_page to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.

WHY IT NEEDS A POLICY

Why set_current_page needs a policy

While changing the current page doesn't directly create or delete document content, it modifies the navigational/session state of the Figma document, which is a reversible write operation. The impact is localized to the user's view of the document and poses minimal risk in an automated context. No data is destroyed, no financial transactions occur, and no code execution is triggered.

From the tool's definition The tool 'set_current_page' performs a state change by switching to a specific page in the Figma document. The description uses 'Switch to', indicating a modification of the current application state rather than a mere read operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_current_page Rate-limited

set_current_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_current_page": {
      "limits": [
        {
          "counter": "set_current_page_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Talk to Figma MCP, so you can run agents against it safely.

FAQ

Questions about set_current_page

What does the set_current_page tool do? +

Switch to a specific page in the Figma document. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_current_page? +

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

What risk level is set_current_page? +

set_current_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_current_page? +

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

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

set_current_page is provided by the Claude Talk to Figma MCP server (stranyer/claude-mcp-figma). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.