bts_transport_border_activity_pack
Combine every available official BTS crossing measure for one land-border port into a provenance-backed current-versus-prior activity evidence pack. Keeps trucks, trains, buses, vehicles, passengers, and pedestrians separate while reporting window totals, completeness, and percent change. Use thi...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bts-transport-border-activity-pack.md
What bts_transport_border_activity_pack does on Livedatalink
AI agents invoke bts_transport_border_activity_pack to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
trailing_months | integer | — | Months per current/prior comparison window. Default 12. |
Parameters from the server's own tool schema.
Why bts_transport_border_activity_pack is rated High
bts_transport_border_activity_pack triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bts_transport_border_activity_pack 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_activity_pack, this is the rule to start with:
bts_transport_border_activity_pack stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_activity_pack call is checked against it from then on.
Questions about bts_transport_border_activity_pack
Combine every available official BTS crossing measure for one land-border port into a provenance-backed current-versus-prior activity evidence pack. Keeps trucks, trains, buses, vehicles, passengers, and pedestrians separate while reporting window totals, completeness, and percent change. Use this for 'build a border activity pack for Laredo', 'what changed at Otay Mesa?', or a logistics/corridor briefing. It never fabricates a total across incompatible measures and is not a congestion or wait-time measure. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
bts_transport_border_activity_pack accepts 3 parameters: port, response_format, trailing_months. Required: port. 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_activity_pack: 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_activity_pack is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bts_transport_border_activity_pack 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_activity_pack. 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_activity_pack 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.
Across the catalogue