fmcsa_carrier_search
Search for trucking companies, freight carriers, or motor carriers by company name. Find any carrier's DOT number, MC number, location, fleet size, and operating status. Supports partial name matching. Use this for questions like 'find this trucking company', 'what's the DOT number for Werner?', ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fmcsa-carrier-search.md
What fmcsa_carrier_search does on Livedatalink
AI agents call fmcsa_carrier_search 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 |
|---|---|---|---|
name | string | Yes |
Parameters from the server's own tool schema.
Why fmcsa_carrier_search is rated Low
This tool retrieves publicly available regulatory data from the FMCSA national database about commercial motor carriers. It performs lookups and searches with no side effects—no data is created, modified, deleted, or executed. The information returned (DOT numbers, MC numbers, location, fleet size, operating status) is factual reference data about registered carriers.
From the tool's definition Tool description explicitly states 'Search for trucking companies' and 'Find any carrier's DOT number, MC number, location, fleet size, and operating status.' The verb 'Search' and 'Find' indicate data retrieval.
Attacks that exploit this kind of access
The rule that runs fmcsa_carrier_search 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 fmcsa_carrier_search, this is the rule to start with:
fmcsa_carrier_search 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 fmcsa_carrier_search call is checked against it from then on.
Questions about fmcsa_carrier_search
Search for trucking companies, freight carriers, or motor carriers by company name. Find any carrier's DOT number, MC number, location, fleet size, and operating status. Supports partial name matching. Use this for questions like 'find this trucking company', 'what's the DOT number for Werner?', 'search for freight carriers in Texas', 'look up this logistics company', or any carrier name search. Returns up to 50 matching carriers from the FMCSA national database. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fmcsa_carrier_search accepts 1 parameter: name. Required: name. 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 fmcsa_carrier_search: 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.
fmcsa_carrier_search 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 fmcsa_carrier_search 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 fmcsa_carrier_search. 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.
fmcsa_carrier_search 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