New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

bts_transport_search_ports

Search U.S. land-border ports in LiveDataLink's self-hosted official BTS Border Crossing Entry snapshot. Returns stable four-digit port codes, state, Canada/Mexico border, coordinates, available crossing measures, coverage, pagination, and source provenance. Use this for 'find the Laredo border p...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 60 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/bts-transport-search-ports.md

What bts_transport_search_ports does on Livedatalink

AI agents call bts_transport_search_ports 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.

ParameterTypeRequiredDescription
limit integer — Maximum ports. Default 20.
query string — Port name, state, or exact four-digit port code.
state string — Exact state name, such as Texas or New York.
border string — Optional official BTS border label.
offset integer — Ports to skip. Default 0.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why bts_transport_search_ports is rated Low

Even though bts_transport_search_ports 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.

Questions about bts_transport_search_ports

What does the bts_transport_search_ports tool do? +

Search U.S. land-border ports in LiveDataLink's self-hosted official BTS Border Crossing Entry snapshot. Returns stable four-digit port codes, state, Canada/Mexico border, coordinates, available crossing measures, coverage, pagination, and source provenance. Use this for 'find the Laredo border port code', 'which Arizona ports have truck crossings?', or to resolve a port before a trend call. Inbound land ports only; not wait times or outbound traffic. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does bts_transport_search_ports accept? +

bts_transport_search_ports accepts 6 parameters: limit, query, state, border, offset, response_format. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bts_transport_search_ports? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for bts_transport_search_ports: 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.

What risk level is bts_transport_search_ports? +

bts_transport_search_ports is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bts_transport_search_ports? +

Yes. Add a rate_limit block to the bts_transport_search_ports 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.

How do I block bts_transport_search_ports completely? +

Set action: deny in the PolicyLayer policy for bts_transport_search_ports. 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.

What MCP server provides bts_transport_search_ports? +

bts_transport_search_ports 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.