verify_domain

Run DNS verification for a domain and enqueue SSL issuance.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/verify-domain.md

WHAT IT DOES

What verify_domain does on Webcake Storefront

AI agents invoke verify_domain to trigger actions in Webcake Storefront. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why verify_domain is rated High

This tool triggers external operations: it actively runs a DNS verification check and enqueues an SSL certificate issuance process. These are side-effectful external operations (not just reads), but they are not destructive, financial, or simple writes — they trigger external processes whose effects depend on the domain argument, fitting the Execute category.

From the tool's definition Run DNS verification for a domain and enqueue SSL issuance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_domain safely

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

verify_domain Rate-limited

verify_domain stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_domain": {
      "limits": [
        {
          "counter": "verify_domain_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about verify_domain

What does the verify_domain tool do? +

Run DNS verification for a domain and enqueue SSL issuance. It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_domain? +

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

What risk level is verify_domain? +

verify_domain is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit verify_domain? +

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

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

verify_domain is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools → High-risk tools on this server →

Across the catalogue

disable_modsecurity_domain on cPanel MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →