sandbox_domain_remove

Detach a custom domain from a sandbox.

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-domain-remove.md

WHAT IT DOES

What sandbox_domain_remove does on EasyBits

AI agents call sandbox_domain_remove to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why sandbox_domain_remove is rated Critical

Irreversibly removes domain association; cannot be undone without reconfiguration.

From the tool's definition Detach a custom domain from a sandbox; removes domain binding.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_domain_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_domain_remove, this is the rule to start with:

sandbox_domain_remove Hidden

sandbox_domain_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sandbox_domain_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_domain_remove call is checked against it from then on.

FAQ

Questions about sandbox_domain_remove

What does the sandbox_domain_remove tool do? +

Detach a custom domain from a sandbox. It is categorised as a Destructive tool in the EasyBits 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 sandbox_domain_remove? +

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

What risk level is sandbox_domain_remove? +

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

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

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

sandbox_domain_remove is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →delete_addon_domain on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →