nbi.infrastructure.bridge_detail
Retrieve the full NBI record for a specific US highway bridge identified by state FIPS code and NBI structure number. Returns all inspection and inventory fields: condition ratings (deck, superstructure, substructure, channel, culvert), load ratings (operating and inventory, in tons), structural ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nbi.infrastructure.bridge-detail.md
What nbi.infrastructure.bridge_detail does on Apibase
AI agents call nbi.infrastructure.bridge_detail 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 |
|---|---|---|---|
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. |
structure_number | string | Yes | NBI structure number — the unique bridge identifier within the state (e.g. "06 0021", "27 0052"). Obtainable from the structure_number field in nbi.search or nb |
Parameters from the server's own tool schema.
Why nbi.infrastructure.bridge_detail is rated Low
Tool retrieves bridge inspection and inventory data from US National Bridge Inventory with no modification or deletion capability.
From the tool's definition Retrieve the full NBI record for a specific US highway bridge
Attacks that exploit this kind of access
The rule that runs nbi.infrastructure.bridge_detail 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.bridge_detail, this is the rule to start with:
nbi.infrastructure.bridge_detail 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.bridge_detail call is checked against it from then on.
Questions about nbi.infrastructure.bridge_detail
Retrieve the full NBI record for a specific US highway bridge identified by state FIPS code and NBI structure number. Returns all inspection and inventory fields: condition ratings (deck, superstructure, substructure, channel, culvert), load ratings (operating and inventory, in tons), structural evaluation, waterway adequacy, posting/closure status, scour-critical rating, deck area (m²), approach details, owner and maintenance agency, functional classification, design load, deck structure/surface/membrane type, improvement costs, inspection frequency and date, fracture-critical designation, federal lands flag, and skew angle. Use nbi.search or nbi.nearby to discover structure numbers before calling this tool. Data: FHWA NBI as of June 2023. 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.bridge_detail accepts 2 parameters: state_code, structure_number. Required: state_code, structure_number. 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.bridge_detail: 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.bridge_detail 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.bridge_detail 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.bridge_detail. 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.bridge_detail 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