domain_detect_ip

Detect if machine has a public IP (static_public, dynamic_public, or private_nat).

SERVERYaver SOURCEyaver-cli

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/io-github-kivanccakmak-yaver/domain-detect-ip.md

WHAT IT DOES

What domain_detect_ip does on Yaver

AI agents call domain_detect_ip 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.

RISK

Why domain_detect_ip is rated Low

This tool retrieves and reports network configuration metadata (IP type detection). It performs passive inspection of the machine's IP status without creating, modifying, executing arbitrary operations, or causing destructive effects. The classification is Read as it is purely informational.

From the tool's definition Tool name and description indicate information retrieval: "Detect if machine has a public IP" - queries network configuration state without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

domain_detect_ip Allowed

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

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

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

FAQ

Questions about domain_detect_ip

What does the domain_detect_ip tool do? +

Detect if machine has a public IP (static_public, dynamic_public, or private_nat). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on domain_detect_ip? +

Register the Yaver MCP server in PolicyLayer and add a rule for domain_detect_ip: 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.

What risk level is domain_detect_ip? +

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

Can I rate-limit domain_detect_ip? +

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

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

domain_detect_ip 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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