This record as markdown: /tools/io-github-kivanccakmak-yaver/public-ip.md
What public_ip does on Yaver
AI agents call public_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.
Why public_ip is rated Low
This tool queries and returns the public IP address of the device—a read-only operation with no side effects, no code execution, and no data modification. The only mild concern is information disclosure (knowing the IP could be used for reconnaissance), but this is minimal context and the operation itself is purely informational. Classified as Read/low severity.
From the tool's definition Tool name 'public_ip' and description 'Get public IP address' indicate a query operation that retrieves network information without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs public_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 public_ip, this is the rule to start with:
public_ip 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 public_ip call is checked against it from then on.
Questions about public_ip
Get public IP address. 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 public_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.
public_ip 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 public_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.
Set action: deny in the PolicyLayer policy for public_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.
public_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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue