getGeocoding
Converts a place name into latitude and longitude. Requires city; narrow with state, country or zipcode. For the reverse direction use /reversegeocoding.
This record as markdown: /tools/com-api-ninjas-mcp/getgeocoding.md
What getGeocoding does on API Ninjas
AI agents call getGeocoding to retrieve information from API Ninjas 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 |
|---|---|---|---|
city | string | Yes | City name. |
state | string | — | US state (for United States cities only). |
country | string | — | Country name, 2-letter ISO country code, or 3-letter ISO country code. |
zipcode | string | — | 5-digit zipcode (for United States cities only). |
Parameters from the server's own tool schema.
Why getGeocoding is rated Low
Even though getGeocoding 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 getGeocoding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getGeocoding, this is the rule to start with:
getGeocoding 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 API Ninjas, apply this rule, and every getGeocoding call is checked against it from then on.
Questions about getGeocoding
Converts a place name into latitude and longitude. Requires city; narrow with state, country or zipcode. For the reverse direction use /reversegeocoding. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getGeocoding accepts 4 parameters: city, state, country, zipcode. Required: city. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getGeocoding: 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 API Ninjas. Nothing to install.
getGeocoding 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 getGeocoding 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 getGeocoding. 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.
getGeocoding is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue