nbi.infrastructure.search
Search the National Bridge Inventory (NBI) for highway bridges in a US state, with optional filter by overall condition (Good / Fair / Poor). Returns up to 200 bridges per call, sorted by lowest sufficiency rating first. Each result includes: structure number, location, feature below (river/road)...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nbi.infrastructure.search.md
What nbi.infrastructure.search does on Apibase
AI agents call nbi.infrastructure.search 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 bridges to return (1–200, default 50). Sorted by lowest sufficiency rating ascending. |
condition | string | — | Filter by overall bridge condition: G = Good, F = Fair, P = Poor. Omit to return all conditions. |
state_code | string | Yes | Two-digit FIPS state code (e.g. "06" for California, "48" for Texas, "36" for New York, "17" for Illinois). Leading zero required for single-digit states (e.g. |
Parameters from the server's own tool schema.
Why nbi.infrastructure.search is rated Low
Tool only queries and retrieves bridge infrastructure data with no side effects.
From the tool's definition Search the National Bridge Inventory... Returns up to 200 bridges
Attacks that exploit this kind of access
The rule that runs nbi.infrastructure.search 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.search, this is the rule to start with:
nbi.infrastructure.search 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.search call is checked against it from then on.
Questions about nbi.infrastructure.search
Search the National Bridge Inventory (NBI) for highway bridges in a US state, with optional filter by overall condition (Good / Fair / Poor). Returns up to 200 bridges per call, sorted by lowest sufficiency rating first. Each result includes: structure number, location, feature below (river/road), facility carried, coordinates, year built/reconstructed, overall bridge condition, deck/superstructure/substructure ratings (0–9 scale), operating load rating (tons), max span length (m), deck width (m), average daily traffic, open/posted/closed status, sufficiency rating, and scour-critical classification. Covers 621,000+ bridges on public roads across all 50 states plus territories. Data: FHWA NBI as of June 2023, updated annually. No auth required — USDOT public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nbi.infrastructure.search accepts 3 parameters: limit, condition, state_code. Required: state_code. 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.search: 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.search 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.search 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.search. 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.search 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