carrier_vetting_score
Vet a US motor carrier (trucking company) for a freight-brokerage 'is this safe and legit to broker a load to?' decision, in one call. Give a USDOT number, MC number, or carrier name. Joins FMCSA safety data (operating authority, insurance on file, BASIC safety scores, crash and out-of-service hi...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/carrier-vetting-score.md
What carrier_vetting_score does on Livedatalink
AI agents call carrier_vetting_score 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 | — | MC (motor carrier) number, without the 'MC-' prefix. Used if no DOT number is given. |
dot | number | — | USDOT number of the carrier (most precise). Example: 76830. |
name | string | — | Carrier legal name, used if no DOT/MC number is given. The top FMCSA name match is vetted; prefer a DOT number for an exact carrier. |
Parameters from the server's own tool schema.
Why carrier_vetting_score is rated Low
Even though carrier_vetting_score 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 carrier_vetting_score 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 carrier_vetting_score, this is the rule to start with:
carrier_vetting_score 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 carrier_vetting_score call is checked against it from then on.
Questions about carrier_vetting_score
Vet a US motor carrier (trucking company) for a freight-brokerage 'is this safe and legit to broker a load to?' decision, in one call. Give a USDOT number, MC number, or carrier name. Joins FMCSA safety data (operating authority, insurance on file, BASIC safety scores, crash and out-of-service history vs the national average, safety rating) with sanctions screening (OFAC/UN/EU/BIS on the carrier's legal name), federal-court litigation history (CourtListener), and USAspending federal awards. Returns a GO / CAUTION / NO-GO verdict with the reasons, plus all the underlying fields. NO-GO is triggered by a sanctions match or lack of active operating authority; CAUTION by BASIC alerts, fatal crashes, missing liability insurance, high out-of-service rates, or litigation. This is an analytical aid, not a substitute for your own carrier-onboarding checks. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
carrier_vetting_score accepts 3 parameters: mc, dot, 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 carrier_vetting_score: 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.
carrier_vetting_score 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 carrier_vetting_score 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 carrier_vetting_score. 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.
carrier_vetting_score 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