AI agents call get_public_ip to retrieve information from HackerMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries network information and returns data without modifying, executing code, deleting resources, or committing financial obligations. It is a straightforward read operation.
From the tool's definition Tool description states 'Get your public IP address' — a retrieval operation with no side effects. Returns information only.
Attacks that exploit this kind of access
Get your public IP address. It is categorised as a Read tool in the HackerMCP MCP Server, which means it retrieves data without modifying state.
Register the Hacker MCP server in PolicyLayer and add a rule for get_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 HackerMCP. Nothing to install.
get_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 get_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 get_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.
get_public_ip is provided by the Hacker MCP server (r3versein/hackermcp). 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 →