bts_transport_border_trend
Return a bounded monthly history for one official BTS land-border port and one consistent crossing measure from the self-hosted snapshot. Includes exact month, crossing count, stable port identity, pagination, source hash, and provenance. Use this for 'monthly truck crossings at Laredo', 'pedestr...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bts-transport-border-trend.md
What bts_transport_border_trend does on Livedatalink
AI agents call bts_transport_border_trend to retrieve information from Livedatalink 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 |
|---|---|---|---|
port | string | Yes | Exact BTS four-digit port code or an unambiguous U.S. land-border port name. Search first when needed. |
limit | integer | — | Maximum monthly observations. Default 24. |
offset | integer | — | Observations to skip. Default 0. |
measure | string | Yes | Official BTS crossing measure. Measures have different units and must not be added together. |
end_month | string | — | Calendar month in YYYY-MM format. |
start_month | string | — | Calendar month in YYYY-MM format. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why bts_transport_border_trend is rated Low
Even though bts_transport_border_trend only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs bts_transport_border_trend safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bts_transport_border_trend, this is the rule to start with:
bts_transport_border_trend 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 Livedatalink, apply this rule, and every bts_transport_border_trend call is checked against it from then on.
Questions about bts_transport_border_trend
Return a bounded monthly history for one official BTS land-border port and one consistent crossing measure from the self-hosted snapshot. Includes exact month, crossing count, stable port identity, pagination, source hash, and provenance. Use this for 'monthly truck crossings at Laredo', 'pedestrian crossings at San Ysidro since 2023', or a reproducible port-volume chart. Counts inbound crossing events, not unique vehicles or people. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
bts_transport_border_trend accepts 7 parameters: port, limit, offset, measure, end_month, start_month, response_format. Required: port, measure. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for bts_transport_border_trend: 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 Livedatalink. Nothing to install.
bts_transport_border_trend 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_border_trend 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_border_trend. 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_border_trend is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue