Critical Risk →

change-extension-installation

Install or uninstall a Netlify extension

Risk signalsRemoves installed extensions

Part of the Netlify server.

change-extension-installation can permanently delete data in Netlify, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NETLIFY →

Free to start. No card required.

AI agents may call change-extension-installation to permanently remove or destroy resources in Netlify. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call change-extension-installation in a loop, permanently destroying resources in Netlify. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "change-extension-installation"
  ]
}

See the full Netlify policy for all 19 tools.

Get this rule live on your own Netlify server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NETLIFY →

View all 19 tools →

These attack patterns abuse exactly the kind of access change-extension-installation gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so change-extension-installation only ever does what you allow.

SECURE NETLIFY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the change-extension-installation tool do? +

Install or uninstall a Netlify extension. It is categorised as a Destructive tool in the Netlify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on change-extension-installation? +

Register the Netlify MCP server in PolicyLayer and add a rule for change-extension-installation: 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. Nothing to install.

What risk level is change-extension-installation? +

change-extension-installation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit change-extension-installation? +

Yes. Add a rate_limit block to the change-extension-installation 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 change-extension-installation completely? +

Set action: deny in the PolicyLayer policy for change-extension-installation. 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 change-extension-installation? +

change-extension-installation is provided by the Netlify MCP server (@@netlify/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Netlify tool call.

Deterministic rules across all 19 Netlify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.