PUBLIC, NO API KEY required. Same as check_domain_public but checks up to 50 domains in ONE call (faster + fewer rate-limit hits). Returns an array where each item has availability, price, renewal price, registrar, and a clickable buyUrl. ALWAYS prefer this over multiple check_domain_public calls...
Part of the Namemyapp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_domains_public_bulk to retrieve information from Namemyapp 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 check_domains_public_bulk 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.
tools:
check_domains_public_bulk:
rules:
- action: allowSee the full Namemyapp policy for all 13 tools.
Agents calling read-class tools like check_domains_public_bulk have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
PUBLIC, NO API KEY required. Same as check_domain_public but checks up to 50 domains in ONE call (faster + fewer rate-limit hits). Returns an array where each item has availability, price, renewal price, registrar, and a clickable buyUrl. ALWAYS prefer this over multiple check_domain_public calls when you have more than one candidate. For 5 brandable .ai suggestions, this is one call instead of five.. It is categorised as a Read tool in the Namemyapp MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_domains_public_bulk. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Namemyapp MCP server.
check_domains_public_bulk is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_domains_public_bulk rule in your Intercept 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.
Set action: deny in the Intercept policy for check_domains_public_bulk. 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.
check_domains_public_bulk is provided by the Namemyapp MCP server (@namemyapp/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.