Low Risk

bulk_available

Batch check domain availability with pricing. Check up to 10 domains per call. This is the verification gate — any domain recommended to a user must pass through this tool first. Do not present domains as available based on other tools' signals (e.g., tld_check showing 'might_available', or domai...

Risk signalsBulk/mass operation — affects multiple targets

Part of the DomainKits server.

bulk_available is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DOMAINKITS →

Free to start. No card required.

AI agents call bulk_available to retrieve information from DomainKits without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though bulk_available only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bulk_available": {}
  }
}

See the full DomainKits policy for all 38 tools.

Get this rule live on your own DomainKits server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DOMAINKITS →

View all 38 tools →

These attack patterns abuse exactly the kind of access bulk_available gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so bulk_available only ever does what you allow.

SECURE DOMAINKITS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the bulk_available tool do? +

Batch check domain availability with pricing. Check up to 10 domains per call. This is the verification gate — any domain recommended to a user must pass through this tool first. Do not present domains as available based on other tools' signals (e.g., tld_check showing 'might_available', or domains found in deleted/expired feeds) without confirming here. Input format: comma-separated full domain names including TLD (e.g., 'aitools.com,getai.io,smartai.app'). Maximum 10 per call — for larger batches, make multiple calls. Interpreting results: - status 'available': Confirmed registrable. price and reg_url will be present. - status 'registered': Currently owned — not available for standard registration. - status 'expiring': In the expiration pipeline — can be backordered, not directly registered. reg_url will point to a backorder service. - status 'reserved': Registry-reserved domain — not available for registration. - status 'unknown': Check was inconclusive — do not assume available or unavailable. Best practices: - Always disclose affiliate links when aff=true. - When multiple domains return available, prioritize shorter names and .com over alternatives when presenting results. - If all checked domains come back registered, this is useful signal in itself — the namespace is saturated for that keyword pattern.. It is categorised as a Read tool in the DomainKits MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bulk_available? +

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

What risk level is bulk_available? +

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

Can I rate-limit bulk_available? +

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

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

bulk_available is provided by the DomainKits MCP server (https://api.domainkits.com/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DomainKits tool call.

Deterministic rules across all 38 DomainKits tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.