New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

unhabitat.urban.land_consumption

Retrieve city-level land consumption rate (LCR) versus population growth rate (PGR) data for SDG 11.3.1. Covers 581 cities with measurements for the 1990–2000 and 2000–2015 periods. A LCR/PGR ratio > 1 indicates urban sprawl (land expanding faster than population). Includes built-up area per capi...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/unhabitat.urban.land-consumption.md

What unhabitat.urban.land_consumption does on Apibase

AI agents call unhabitat.urban.land_consumption to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
city string — Filter by city name (partial match, e.g. "Nairobi", "Lagos", "Mumbai"). Case-insensitive.
limit integer — Maximum number of cities to return (1–100, default 50).
region string — Filter by UN-Habitat region (partial match). Regions include "Sub-Saharan Africa", "Northern America and Europe", "Eastern and South-Eastern Asia", "Central and
country string — Filter by country name (partial match, e.g. "Kenya", "United States", "Brazil"). Case-insensitive.

Parameters from the server's own tool schema.

Why unhabitat.urban.land_consumption is rated Low

Queries historical urban development metrics without modifying data or triggering external operations.

From the tool's definition Retrieve city-level land consumption rate data, filter by country, city, region.

Questions about unhabitat.urban.land_consumption

What does the unhabitat.urban.land_consumption tool do? +

Retrieve city-level land consumption rate (LCR) versus population growth rate (PGR) data for SDG 11.3.1. Covers 581 cities with measurements for the 1990–2000 and 2000–2015 periods. A LCR/PGR ratio > 1 indicates urban sprawl (land expanding faster than population). Includes built-up area per capita (m²/person) at three time points. Filter by country, city, or UN region. Useful for sustainable urbanization and land-use planning analysis. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does unhabitat.urban.land_consumption accept? +

unhabitat.urban.land_consumption accepts 4 parameters: city, limit, region, country. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on unhabitat.urban.land_consumption? +

Register the Apibase MCP server in PolicyLayer and add a rule for unhabitat.urban.land_consumption: 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 Apibase. Nothing to install.

What risk level is unhabitat.urban.land_consumption? +

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

Can I rate-limit unhabitat.urban.land_consumption? +

Yes. Add a rate_limit block to the unhabitat.urban.land_consumption 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 unhabitat.urban.land_consumption completely? +

Set action: deny in the PolicyLayer policy for unhabitat.urban.land_consumption. 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 unhabitat.urban.land_consumption? +

unhabitat.urban.land_consumption is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Apibase, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.