bts.aviation.traffic
Query T100 airline segment statistics from BTS giving passenger counts, departures, seats, load factor, and payload by US airport. Filter by IATA airport code (e.g. ATL, JFK, LAX, ORD) and year/period (annual "2025" or quarterly "2026M1-3"). Data covers all US commercial service airports through ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bts.aviation.traffic.md
What bts.aviation.traffic does on Apibase
AI agents call bts.aviation.traffic 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 |
|---|---|---|---|
year | string | — | Year or period to filter by. Annual values use format "YYYY" (e.g. "2025"). Quarterly use "YYYYQn" (e.g. "2026M1-3" for Q1 2026). Latest available is 2026M1-3. |
limit | integer | — | Maximum number of airport traffic records to return (1–500, default 20). |
airport_code | string | — | IATA airport code to filter by (e.g. "ATL" for Atlanta, "JFK" for New York JFK, "LAX" for Los Angeles). Returns top airports if omitted. |
Parameters from the server's own tool schema.
Why bts.aviation.traffic is rated Low
Retrieves public US aviation data with no side effects, modifications, or external operations.
From the tool's definition Query T100 airline segment statistics, passenger counts, departures, seats, load factor
Attacks that exploit this kind of access
The rule that runs bts.aviation.traffic 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 bts.aviation.traffic, this is the rule to start with:
bts.aviation.traffic 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 bts.aviation.traffic call is checked against it from then on.
Questions about bts.aviation.traffic
Query T100 airline segment statistics from BTS giving passenger counts, departures, seats, load factor, and payload by US airport. Filter by IATA airport code (e.g. ATL, JFK, LAX, ORD) and year/period (annual "2025" or quarterly "2026M1-3"). Data covers all US commercial service airports through the most recent quarter. Source: BTS T100 Segment Summary By Origin Airport (Socrata r495-tyji). No auth — US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bts.aviation.traffic accepts 3 parameters: year, limit, airport_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 bts.aviation.traffic: 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.
bts.aviation.traffic 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 bts.aviation.traffic 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 bts.aviation.traffic. 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.
bts.aviation.traffic 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