AI agents call local_public_ip to retrieve information from Net without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns the public IP address associated with the local system. It has no side effects, does not modify data, does not execute arbitrary code or commands, and does not involve financial transactions or destructive operations. It is a pure Read operation with minimal security impact even if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] the public IP address of the local machine' — a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Get the public IP address of the local machine. It is categorised as a Read tool in the Net MCP Server, which means it retrieves data without modifying state.
Register the Net MCP server in PolicyLayer and add a rule for local_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 Net. Nothing to install.
local_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 local_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 local_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.
local_public_ip is provided by the Net MCP server (steelcutoatmeal/net-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →