This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/neon-create-branch.md
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.
| 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 neon_create_branch is rated Medium
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
The rule that runs neon_create_branch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neon_create_branch, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every neon_create_branch call is checked against it from then on.
Questions about neon_create_branch
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.
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.
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.
neon_create_branch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue