geocode
utilpeek: offline geocoding over the GeoNames cities15000 table. For places of a kind nearby use find_places_nearby. Input: either place alone or lat and lon together. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code or a US state code); no match is a ...
This record as markdown: /tools/dev-tanod-tanod/geocode.md
What geocode does on Tanod
AI agents call geocode to retrieve information from Tanod 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 |
|---|---|---|---|
lat | object | — | Reverse: latitude (-90..90); give lat and lon together, or place. |
lon | object | — | Reverse: longitude (-180..180); give lat and lon together, or place. |
place | object | — | Forward: city name, optionally "City, CC" (ISO country or US state code); give place alone, or lat and lon. |
Parameters from the server's own tool schema.
Why geocode is rated Low
Even though geocode only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs geocode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geocode, this is the rule to start with:
geocode 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 Tanod, apply this rule, and every geocode call is checked against it from then on.
Questions about geocode
utilpeek: offline geocoding over the GeoNames cities15000 table. For places of a kind nearby use find_places_nearby. Input: either place alone or lat and lon together. place matches cities of 15,000+ people offline ("City" or "City, CC" with an ISO country code or a US state code); no match is a 404 place_not_found (not charged). Cities only (no street addresses). Typically under 0.1 s (first call up to 1 s). Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Data: GeoNames (geonames.org) cities15000, CC BY 4.0; credit it when you show or republish it (the attribution field carries the text). Docs: https://tanod.dev/learn/reverse-geocoding-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
geocode accepts 3 parameters: lat, lon, place. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for geocode: 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 Tanod. Nothing to install.
geocode 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 geocode 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 geocode. 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.
geocode is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue