// SCAN REPORT

Netlify

19 tools. 9 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 5 Apr 2026

9 can modify or destroy data

10 read-only

19 tools total

// TOOL MAP

Read (10) Write / Execute (8) Destructive / Financial (1)

// WHAT CAN GO WRONG

Destructive tools (change-extension-installation) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (create-new-project, manage-env-vars, manage-form-submissions) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (deploy-site, initialize-database) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Netlify. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @@netlify/mcp

Scans every tool. Generates a policy. Starts enforcing.

Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client

// RECOMMENDED RULES

Deny destructive operations

change-extension-installation:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

create-new-project:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

get-deploy:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 19 NETLIFY TOOLS

DESTRUCTIVE 1 tools

Destructive change-extension-installation

EXECUTE 2 tools

Execute deploy-site Execute initialize-database

WRITE 6 tools

Write create-new-project Write manage-env-vars Write manage-form-submissions Write update-forms Write update-project-name Write update-visitor-access-controls

READ 10 tools

Read get-deploy Read get-deploy-for-site Read get-extensions Read get-forms-for-project Read get-full-extension-details Read get-project Read get-projects Read get-team Read get-teams Read get-user

// FAQ

Can an AI agent delete data through the Netlify MCP server? +

Yes. The Netlify server exposes 1 destructive tools including change-extension-installation. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Netlify? +

The Netlify server has 6 write tools including create-new-project, manage-env-vars, manage-form-submissions. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Netlify MCP server expose? +

19 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 9 can modify, create, or delete data.

How do I add Intercept to my Netlify setup? +

One line change. Instead of running the Netlify server directly, prefix it with Intercept: intercept -c netlify.yaml -- npx -y @@@netlify/mcp. Download a pre-built policy from policylayer.com/policies/netlify and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init

Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.

Netlify

One command. Full control.

Other MCP servers with similar tools.

Control every MCP tool call your agent makes.

Control every MCP tool call
your agent makes.