geocoding_search

Search Nominatim places. Returns typed Nominatim JSONv2 forward geocoding results. Use either q or structured fields, not both.

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/geocoding-search.md

WHAT IT DOES

What geocoding_search does on Crawlora

AI agents call geocoding_search 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
`q`	string	—	Free-text search query
`city`	string	—	Structured city
`limit`	integer	—	Maximum results, defaults to 10 and clamps to 20
`state`	string	—	Structured state
`county`	string	—	Structured county
`street`	string	—	Structured street or house number
`country`	string	—	Structured country
`extratags`	boolean	—	Include OSM extra tags
`postalcode`	string	—	Structured postal code
`namedetails`	boolean	—	Include multilingual name details
`countrycodes`	string	—	Comma-separated ISO 3166-1 alpha-2 country filters
`addressdetails`	boolean	—	Include address details, defaults to true

Parameters from the server's own tool schema.

RISK

Why geocoding_search is rated Low

Even though geocoding_search 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.

Risk signalsHigh parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs geocoding_search 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_search, this is the rule to start with:

geocoding_search Allowed

geocoding_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "geocoding_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every geocoding_search call is checked against it from then on.

FAQ

Questions about geocoding_search

What does the geocoding_search tool do? +

Search Nominatim places. Returns typed Nominatim JSONv2 forward geocoding results. Use either q or structured fields, not both. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.

What parameters does geocoding_search accept? +

geocoding_search accepts 12 parameters: q, city, limit, state, county, street, country, extratags, postalcode, namedetails, countrycodes, addressdetails. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on geocoding_search? +

Register the Crawlora MCP server in PolicyLayer and add a rule for geocoding_search: 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.

What risk level is geocoding_search? +

geocoding_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geocoding_search? +

Yes. Add a rate_limit block to the geocoding_search 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.

How do I block geocoding_search completely? +

Set action: deny in the PolicyLayer policy for geocoding_search. 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.

What MCP server provides geocoding_search? +

geocoding_search 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.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →