sandbox_domain_verify

Check whether a custom domain is live: confirms DNS resolves and that https://<domain> serves with a valid TLS cert. Use after the customer sets the CNAME to tell them whether it

SERVEREasyBits SOURCE@easybits.cloud/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What sandbox_domain_verify does on EasyBits

AI agents call sandbox_domain_verify to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sandbox_domain_verify is rated Low

Tool queries domain status and DNS resolution without modifying or executing code.

From the tool's definition Check whether a custom domain is live; confirms DNS resolves and HTTPS serves

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_domain_verify 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_verify, this is the rule to start with:

sandbox_domain_verify Allowed

sandbox_domain_verify is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sandbox_domain_verify": {}
  }
}

ALLOW ONLY 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_verify call is checked against it from then on.

FAQ

Questions about sandbox_domain_verify

What does the sandbox_domain_verify tool do? +

Check whether a custom domain is live: confirms DNS resolves and that https://<domain> serves with a valid TLS cert. Use after the customer sets the CNAME to tell them whether it. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sandbox_domain_verify? +

Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_domain_verify: 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_verify? +

sandbox_domain_verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sandbox_domain_verify? +

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

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

sandbox_domain_verify 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →