fmcsa_carrier_lookup
Look up a trucking company, freight carrier, or motor carrier by DOT number or MC number. Returns company name, address, phone, fleet size, number of drivers, safety rating, operating authority, insurance status (BIPD, cargo, bond), crash history, inspection rates, and out-of-service percentages....
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fmcsa-carrier-lookup.md
What fmcsa_carrier_lookup does on Livedatalink
AI agents call fmcsa_carrier_lookup 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 |
|---|---|---|---|
mc_number | integer | — | |
dot_number | integer | — |
Parameters from the server's own tool schema.
Why fmcsa_carrier_lookup is rated Low
This is a pure read operation that queries and retrieves public regulatory data about motor carriers. It enables information lookup and verification but does not create, modify, delete, or execute any operations. The data returned (safety ratings, crash history, inspection rates) is already public information maintained by FMCSA. No financial transactions, code execution, or destructive actions are possible.
From the tool's definition Tool performs lookup/query operations: 'Look up a trucking company', 'Returns company name, address, phone, fleet size, number of drivers, safety rating, operating authority, insurance status, crash history, inspection rates, and out-of-service percentages.'…
Attacks that exploit this kind of access
The rule that runs fmcsa_carrier_lookup 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_lookup, this is the rule to start with:
fmcsa_carrier_lookup 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_lookup call is checked against it from then on.
Questions about fmcsa_carrier_lookup
Look up a trucking company, freight carrier, or motor carrier by DOT number or MC number. Returns company name, address, phone, fleet size, number of drivers, safety rating, operating authority, insurance status (BIPD, cargo, bond), crash history, inspection rates, and out-of-service percentages. Use this for questions like 'is this carrier safe?', 'look up this trucking company', 'check this DOT number', 'verify this carrier', 'what's their safety rating?', or any freight carrier lookup. Covers all US carriers registered with FMCSA. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fmcsa_carrier_lookup accepts 2 parameters: mc_number, dot_number. 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_lookup: 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_lookup 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_lookup 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_lookup. 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_lookup 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