getCityData
Get city data from either a name or population range. Returns a list of cities that satisfies the parameters.
This record as markdown: /tools/com-api-ninjas-mcp/getcitydata.md
What getCityData does on API Ninjas
AI agents call getCityData 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 |
|---|---|---|---|
name | string | — | Name of city. |
limit | integer | — | How many results to return. Must be between 1 and 30. Default is 1. To get more than 30 results, use the offset parameter. Premium only. |
offset | integer | — | Number of results to offset for pagination. Premium only. |
country | string | — | Country filter. Must be an ISO-3166 alpha-2 country code (e.g. US). |
max_lat | number | — | Maximum latitude coordinate. |
max_lon | number | — | Maximum longitude coordinate. |
min_lat | number | — | Minimum latitude coordinate. |
min_lon | number | — | Minimum longitude coordinate. |
max_population | integer | — | Maximum city population. |
min_population | integer | — | Minimum city population. |
Parameters from the server's own tool schema.
Why getCityData is rated Low
Even though getCityData 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 (10 properties)
Attacks that exploit this kind of access
The rule that runs getCityData 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 getCityData, this is the rule to start with:
getCityData 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 getCityData call is checked against it from then on.
Questions about getCityData
Get city data from either a name or population range. Returns a list of cities that satisfies the parameters. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCityData accepts 10 parameters: name, limit, offset, country, max_lat, max_lon, min_lat, min_lon, max_population, min_population. 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 getCityData: 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.
getCityData 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 getCityData 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 getCityData. 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.
getCityData 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