carrier_vetting_batch
Vet a batch of up to 10 US motor carriers by USDOT number in one workflow call. Returns one GO/CAUTION/NO-GO result per carrier, source coverage and failures, key authority/insurance/safety signals, and an export in markdown (default), JSON, or CSV. Each submitted carrier uses one query from your...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/carrier-vetting-batch.md
What carrier_vetting_batch does on Livedatalink
AI agents call carrier_vetting_batch 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 |
|---|---|---|---|
format | string | — | Export format. Defaults to markdown. |
dot_numbers | object | Yes | 1-10 USDOT numbers. A comma-separated string is also accepted for agent convenience. |
Parameters from the server's own tool schema.
Why carrier_vetting_batch is rated Low
Even though carrier_vetting_batch 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_batch 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_batch, this is the rule to start with:
carrier_vetting_batch 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_batch call is checked against it from then on.
Questions about carrier_vetting_batch
Vet a batch of up to 10 US motor carriers by USDOT number in one workflow call. Returns one GO/CAUTION/NO-GO result per carrier, source coverage and failures, key authority/insurance/safety signals, and an export in markdown (default), JSON, or CSV. Each submitted carrier uses one query from your plan because each is evaluated independently. Use this to screen a broker's candidate list or lane roster; one missing or unavailable record does not hide the others. This is an analytical aid, not a substitute for direct FMCSA verification. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
carrier_vetting_batch accepts 2 parameters: format, dot_numbers. Required: dot_numbers. 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_batch: 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_batch 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_batch 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_batch. 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_batch 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