Create a new Netlify site from a GitHub repository
AI agents use createSiteFromGitHub to create or update resources in Netlify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Netlify MCP Server environment.
This tool creates a new Netlify site, which is a reversible operation (the site can be deleted via the sibling deleteSite tool). While it does provision infrastructure and establish CI/CD connections, the core action is resource creation without irreversible data destruction.
From the tool's definition Tool description states "Create a new Netlify site from a GitHub repository" — this creates a new resource (site) and modifies the deployment infrastructure by connecting a GitHub repository to Netlify's hosting platform.
Attacks that exploit this kind of access
Create a new Netlify site from a GitHub repository. It is categorised as a Write tool in the Netlify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Netlify MCP Server MCP server in PolicyLayer and add a rule for createSiteFromGitHub: 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 Netlify MCP Server. Nothing to install.
createSiteFromGitHub 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 createSiteFromGitHub 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 createSiteFromGitHub. 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.
createSiteFromGitHub is provided by the Netlify MCP Server MCP server (mcpflow/netlify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →