nbi.infrastructure.nearby
Find US highway bridges within a specified radius (up to 50 miles) of a latitude/longitude coordinate. Results are sorted by lowest sufficiency rating ascending (most at-risk bridges first). Returns the same core fields as nbi.search: structure number, location, feature below, coordinates, condit...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nbi.infrastructure.nearby.md
What nbi.infrastructure.nearby does on Apibase
AI agents call nbi.infrastructure.nearby 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of nearby bridges to return (1–100, default 25). Sorted by lowest sufficiency rating ascending. |
latitude | number | Yes | Center latitude of the search area in decimal degrees (e.g. 37.7749 for San Francisco). |
longitude | number | Yes | Center longitude of the search area in decimal degrees (e.g. -122.4194 for San Francisco). |
radius_miles | number | — | Search radius in miles from the center point (0.1–50, default 10). Larger radii may return up to 100 results. |
Parameters from the server's own tool schema.
Why nbi.infrastructure.nearby is rated Low
Tool queries public infrastructure data without modification, deletion, or execution capabilities.
From the tool's definition Find US highway bridges within specified radius, returns bridge data fields.
Attacks that exploit this kind of access
The rule that runs nbi.infrastructure.nearby safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nbi.infrastructure.nearby, this is the rule to start with:
nbi.infrastructure.nearby 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 Apibase, apply this rule, and every nbi.infrastructure.nearby call is checked against it from then on.
Questions about nbi.infrastructure.nearby
Find US highway bridges within a specified radius (up to 50 miles) of a latitude/longitude coordinate. Results are sorted by lowest sufficiency rating ascending (most at-risk bridges first). Returns the same core fields as nbi.search: structure number, location, feature below, coordinates, condition (Good/Fair/Poor), deck/superstructure/substructure ratings, operating load rating, max span length, deck width, average daily traffic, open/posted/closed status, and scour classification. Useful for infrastructure planning, site assessments, disaster response routing, and proximity analysis. Covers all 621,000+ US highway bridges. No auth required — USDOT/FHWA public domain data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nbi.infrastructure.nearby accepts 4 parameters: limit, latitude, longitude, radius_miles. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for nbi.infrastructure.nearby: 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.
nbi.infrastructure.nearby 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 nbi.infrastructure.nearby 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 nbi.infrastructure.nearby. 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.
nbi.infrastructure.nearby 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.
This server
Across the catalogue