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

unhabitat.urban.transport_access

Retrieve city-level data on the proportion of urban population with convenient access to public transport (SDG indicator 11.2.1). Covers 1,555 cities across all world regions from the UN-Habitat Urban Indicators Database. Filter by country, city name, or UN region. Returns access percentage and e...

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.transport-access.md

What unhabitat.urban.transport_access does on Apibase

AI agents call unhabitat.urban.transport_access 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.transport_access is rated Low

Tool queries UN-Habitat database for public transit access statistics; no side effects or data modification.

From the tool's definition Retrieve city-level data on proportion of urban population with convenient access to public transport

Questions about unhabitat.urban.transport_access

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

Retrieve city-level data on the proportion of urban population with convenient access to public transport (SDG indicator 11.2.1). Covers 1,555 cities across all world regions from the UN-Habitat Urban Indicators Database. Filter by country, city name, or UN region. Returns access percentage and estimate source per city. Useful for urban mobility analysis, SDG 11 reporting, and comparing public transit equity across cities. 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.transport_access accept? +

unhabitat.urban.transport_access 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.transport_access? +

Register the Apibase MCP server in PolicyLayer and add a rule for unhabitat.urban.transport_access: 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.transport_access? +

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

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

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

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

unhabitat.urban.transport_access 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.