neon_create_branch · UnClick MCP: Risk & Policy

WHAT IT DOES

What neon_create_branch does on UnClick

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

PARAMETERS

Parameter	Type	Required	Description
`api_key`	string	—
`project_id`	string	Yes
`branch_name`	string	—	Name for the new branch

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why neon_create_branch needs a policy

This tool creates a new resource (a database branch) which is a reversible write operation. It doesn't delete data (not Destructive), doesn't execute arbitrary code (not Execute), and doesn't move money (not Financial). The severity is medium because creating branches can consume resources and affect infrastructure, but the action is reversible via deletion.

From the tool's definition Tool name and description: 'Create a new branch in a Neon project' — the verb 'Create' and action 'create a new branch' clearly indicate data creation/modification.

Risk signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

neon_create_branch Rate-limited

neon_create_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": {
    "neon_create_branch": {
      "limits": [
        {
          "counter": "neon_create_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 UnClick, so you can run agents against it safely.

FAQ

Questions about neon_create_branch

What does the neon_create_branch tool do? +

Create a new branch in a Neon project. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does neon_create_branch accept? +

neon_create_branch accepts 3 parameters: api_key, project_id, branch_name. Required: project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neon_create_branch? +

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

What risk level is neon_create_branch? +

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

Can I rate-limit neon_create_branch? +

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

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

neon_create_branch is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.