bts.transport.tsi
Retrieve the BTS Transportation Services Index (TSI), a monthly economic indicator measuring the volume of freight and passenger transportation services across all modes. Returns total TSI, freight TSI, passenger TSI, plus component indices (vehicle miles traveled, rail carloads, transit, petrole...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bts.transport.tsi.md
What bts.transport.tsi does on Apibase
AI agents call bts.transport.tsi 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 monthly records to return (1–300, default 12). |
end_date | string | — | End of date range in YYYY-MM-DD format (e.g. "2024-12-31"). |
start_date | string | — | Start of date range in YYYY-MM-DD format (e.g. "2024-01-01"). Index goes back to 2000. |
Parameters from the server's own tool schema.
Why bts.transport.tsi is rated Low
Tool retrieves historical transportation data with no side effects or modification capability.
From the tool's definition Retrieve the BTS Transportation Services Index (TSI), a monthly economic indicator
Attacks that exploit this kind of access
The rule that runs bts.transport.tsi 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.transport.tsi, this is the rule to start with:
bts.transport.tsi 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.transport.tsi call is checked against it from then on.
Questions about bts.transport.tsi
Retrieve the BTS Transportation Services Index (TSI), a monthly economic indicator measuring the volume of freight and passenger transportation services across all modes. Returns total TSI, freight TSI, passenger TSI, plus component indices (vehicle miles traveled, rail carloads, transit, petroleum/gas pipelines). Base year 2000=100. Data from 2000 to present. Source: BTS TSI dataset (Socrata bw6n-ddqk). 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.transport.tsi accepts 3 parameters: limit, end_date, start_date. 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.transport.tsi: 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.transport.tsi 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.transport.tsi 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.transport.tsi. 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.transport.tsi 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