setup_project_branch · Figma to React MCP: Risk & Policy

WHAT IT DOES

What setup_project_branch does on Figma to React MCP

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

WHY IT NEEDS A POLICY

Why setup_project_branch needs a policy

Creating a branch is a reversible modification to the source control system. It does not delete data (not Destructive), does not move money (not Financial), and while it interacts with GitHub, it is fundamentally a write operation that creates a new resource. The branch can be deleted if needed.

From the tool's definition Tool description states 'Create a new GitHub branch for feature development.' The word 'Create' indicates a write operation that generates a new branch in a GitHub repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_project_branch Rate-limited

setup_project_branch 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": {
    "setup_project_branch": {
      "limits": [
        {
          "counter": "setup_project_branch_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 Figma to React MCP, so you can run agents against it safely.

FAQ

Questions about setup_project_branch

What does the setup_project_branch tool do? +

Create a new GitHub branch for feature development. It is categorised as a Write tool in the Figma to React 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 setup_project_branch? +

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

What risk level is setup_project_branch? +

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

Can I rate-limit setup_project_branch? +

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

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

setup_project_branch is provided by the Figma to React MCP server (surisagar900/figma-to-react-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.