delete_easy_builder_instance

Delete an Easy Builder instance

SERVER20i MCP Server SOURCEcbrown35/20i-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/delete-easy-builder-instance.md

What delete_easy_builder_instance does on 20i MCP Server

AI agents call delete_easy_builder_instance to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_easy_builder_instance is rated Critical

The 'delete' action combined with 'instance' (a discrete, potentially valuable digital asset) constitutes a destructive operation that cannot be undone. Deleting a website builder instance would permanently remove user content, configuration, and potentially impact live websites. This is irreversible data loss.

From the tool's definition Tool name contains 'delete' and description states 'Delete an Easy Builder instance', indicating irreversible removal of a website builder resource.

Questions about delete_easy_builder_instance

What does the delete_easy_builder_instance tool do? +

Delete an Easy Builder instance. It is categorised as a Destructive tool in the 20i MCP Server 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 delete_easy_builder_instance? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for delete_easy_builder_instance: 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 20i MCP Server. Nothing to install.

What risk level is delete_easy_builder_instance? +

delete_easy_builder_instance 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 delete_easy_builder_instance? +

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

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

delete_easy_builder_instance is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 20i MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 20i MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.