geocoding_lookup
Lookup Nominatim OSM ids. Returns typed Nominatim JSONv2 places for comma-separated OSM ids such as W34633854,N123,R456.
This record as markdown: /tools/crawlora-mcp/geocoding-lookup.md
What geocoding_lookup does on Crawlora
AI agents call geocoding_lookup to retrieve information from Crawlora 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 |
|---|---|---|---|
osm_ids | string | Yes | Comma-separated OSM ids such as W34633854,N123,R456 |
extratags | boolean | — | Include OSM extra tags |
namedetails | boolean | — | Include multilingual name details |
addressdetails | boolean | — | Include address details, defaults to true |
accept_language | string | — | Preferred result language, forwarded to Nominatim |
Parameters from the server's own tool schema.
Why geocoding_lookup is rated Low
Even though geocoding_lookup 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 geocoding_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geocoding_lookup, this is the rule to start with:
geocoding_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 Crawlora, apply this rule, and every geocoding_lookup call is checked against it from then on.
Questions about geocoding_lookup
Lookup Nominatim OSM ids. Returns typed Nominatim JSONv2 places for comma-separated OSM ids such as W34633854,N123,R456. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
geocoding_lookup accepts 5 parameters: osm_ids, extratags, namedetails, addressdetails, accept_language. Required: osm_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for geocoding_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 Crawlora. Nothing to install.
geocoding_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 geocoding_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 geocoding_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.
geocoding_lookup is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue