This record as markdown: /tools/io-github-portel-dev-ncp/create-site.md
What create_site does on Ncp
AI agents use create_site to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_site is rated Medium
This tool creates a new site resource, which is reversible (the site can be deleted), so it falls under Write rather than Destructive. The severity is medium because creating a site could incur costs depending on Netlify's pricing model and could consume quota/resources, but the primary risk is resource modification rather than financial obligation (no explicit money movement) or data destruction.
From the tool's definition The tool is named 'create_site' and described as 'Create Netlify site'. This directly creates a new deployable resource (a website hosting site) on the Netlify platform.
Attacks that exploit this kind of access
The rule that runs create_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_site, this is the rule to start with:
create_site 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 Ncp, apply this rule, and every create_site call is checked against it from then on.
Questions about create_site
Create Netlify site. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for create_site: 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 Ncp. Nothing to install.
create_site 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 create_site 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 create_site. 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.
create_site is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue