This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-check.md
What domain_check does on Yaver
AI agents call domain_check to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to check (e.g. myapp.dev) |
Parameters from the server's own tool schema.
Why domain_check is rated Low
This is a straightforward read operation that queries domain registration status. It has no side effects, does not execute code, does not create or modify data, and does not affect financial or destructive resources. The blast radius if misused is minimal (an attacker could enumerate domain availability, but this is already public information).
From the tool's definition The tool description states it 'Check[s] if a domain is available or registered' — a query operation that retrieves status information about a domain without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs domain_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For domain_check, this is the rule to start with:
domain_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every domain_check call is checked against it from then on.
Questions about domain_check
Check if a domain is available or registered. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
domain_check accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for domain_check: 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 Yaver. Nothing to install.
domain_check 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 domain_check 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.
Set action: deny in the PolicyLayer policy for domain_check. 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.
domain_check is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue