High Risk →

navigate_to_page

Switch the active Figma page. Provide either pageId or pageName.

Part of the Figma Mcp Go MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@vkhanhqui/figma-mcp-go Execute Risk 3/5

AI agents invoke navigate_to_page to trigger processes or run actions in Figma Mcp Go. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

navigate_to_page can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

figma-mcp-go.yaml
tools:
  navigate_to_page:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Figma Mcp Go policy for all 73 tools.

Tool Name navigate_to_page
Category Execute
Risk Level High

View all 73 tools →

Agents calling execute-class tools like navigate_to_page have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

navigate_to_page is one of the high-risk operations in Figma Mcp Go. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the navigate_to_page tool do? +

Switch the active Figma page. Provide either pageId or pageName.. It is categorised as a Execute tool in the Figma Mcp Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate_to_page? +

Add a rule in your Intercept YAML policy under the tools section for navigate_to_page. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Figma Mcp Go MCP server.

What risk level is navigate_to_page? +

navigate_to_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit navigate_to_page? +

Yes. Add a rate_limit block to the navigate_to_page rule in your Intercept 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 navigate_to_page completely? +

Set action: deny in the Intercept policy for navigate_to_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 navigate_to_page? +

navigate_to_page is provided by the Figma Mcp Go MCP server (@vkhanhqui/figma-mcp-go). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Figma Mcp Go

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.