geojs_lookup
Get IP geolocation (country, region, city, lat/lon) from GeoJS. Omit IP for self-lookup.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/geojs-lookup.md
What geojs_lookup does on UnClick
AI agents call geojs_lookup to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | — | IP address (optional, defaults to caller IP). |
Parameters from the server's own tool schema.
Why geojs_lookup is rated Low
This tool retrieves geographical information associated with IP addresses. It performs a read-only lookup against a public geolocation database with no capability to modify, delete, execute, or commit financial actions. The only minor consideration is that IP geolocation could support reconnaissance activities, but the tool itself is fundamentally a simple query with negligible blast radius if misused by an AI agent.
From the tool's definition The tool description states 'Get IP geolocation (country, region, city, lat/lon) from GeoJS' — this is purely a data retrieval operation with no side effects. It queries an external geolocation service and returns location data.
Attacks that exploit this kind of access
The rule that runs geojs_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geojs_lookup, this is the rule to start with:
geojs_lookup 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 UnClick, apply this rule, and every geojs_lookup call is checked against it from then on.
Questions about geojs_lookup
Get IP geolocation (country, region, city, lat/lon) from GeoJS. Omit IP for self-lookup. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
geojs_lookup accepts 1 parameter: ip. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for geojs_lookup: 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 UnClick. Nothing to install.
geojs_lookup 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 geojs_lookup 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 geojs_lookup. 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.
geojs_lookup is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue