This record as markdown: /tools/io-github-kivanccakmak-yaver/domain-list.md
What domain_list does on Yaver
AI agents call domain_list 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.
Why domain_list is rated Low
This tool performs a read-only operation that retrieves domain information. There are no side effects, no data modifications, no code execution, and no destructive actions. The blast radius is minimal as it only exposes domain metadata that is typically non-sensitive operational information.
From the tool's definition Tool name is 'domain_list' and description states 'List all domains with SSL status and routing' — purely retrieves and queries domain configuration data with no modification or execution.
Attacks that exploit this kind of access
The rule that runs domain_list 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_list, this is the rule to start with:
domain_list 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_list call is checked against it from then on.
Questions about domain_list
List all domains with SSL status and routing. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for domain_list: 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_list 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_list 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_list. 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_list 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