check_domain

Check whether a domain is available/valid without attaching it.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What check_domain does on Webcake Storefront

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

RISK

Why check_domain is rated Low

This tool retrieves domain availability/validity status without modifying any data or triggering side effects. It performs a read-only lookup operation with no capacity to create, modify, delete, or execute actions. The explicit statement 'without attaching it' reinforces that no state changes occur.

From the tool's definition Tool name is 'check_domain' and description states it 'Check[s] whether a domain is available/valid without attaching it.' The verb 'check' and phrase 'without attaching it' indicate a query operation that retrieves status information without making changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_domain Allowed

check_domain 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": {
    "check_domain": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about check_domain

What does the check_domain tool do? +

Check whether a domain is available/valid without attaching it. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_domain? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for check_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 check_domain? +

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

Can I rate-limit check_domain? +

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

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

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

Across the catalogue

The MCP Attack Database →

Guides

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