carrier_vetting_evidence_pack

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/carrier-vetting-evidence-pack.md

WHAT IT DOES

What carrier_vetting_evidence_pack does on Livedatalink

AI agents use carrier_vetting_evidence_pack to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.

Parameter	Type	Required	Description
`mc`	number \| string	—	MC/MX number. Accepts 123456 or MC-123456.
`dot`	number \| string	—	USDOT number (preferred). Accepts 3405079 or USDOT 3405079.
`name`	string	—	Legal carrier name when DOT/MC is unavailable.

Parameters from the server's own tool schema.

RISK

Why carrier_vetting_evidence_pack is rated Medium

An AI agent can call carrier_vetting_evidence_pack faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs carrier_vetting_evidence_pack 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_evidence_pack, this is the rule to start with:

carrier_vetting_evidence_pack Rate-limited

carrier_vetting_evidence_pack stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "carrier_vetting_evidence_pack": {
      "limits": [
        {
          "counter": "carrier_vetting_evidence_pack_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every carrier_vetting_evidence_pack call is checked against it from then on.

FAQ

Questions about carrier_vetting_evidence_pack

What does the carrier_vetting_evidence_pack tool do? +

Produce an auditable Carrier Vetting Pack for a freight broker. Resolve a US motor carrier by USDOT, MC, or legal name, then return the GO/CAUTION/NO-GO verdict, the exact FMCSA authority/insurance/safety evidence, sanctions/court/federal-award checks, source coverage and failures, retrieval timestamp, primary-source links, a versioned evidence receipt fingerprint, and a broker follow-up checklist. The receipt helps detect accidental changes after export; it is not tamper-proof storage or a compliance certification. This is the evidence-first companion to carrier_vetting_score: use it when a human reviewer needs to save or forward the record. It is an analytical aid, not a substitute for direct FMCSA insurance and authority verification. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does carrier_vetting_evidence_pack accept? +

carrier_vetting_evidence_pack accepts 3 parameters: mc, dot, name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on carrier_vetting_evidence_pack? +

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

carrier_vetting_evidence_pack is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit carrier_vetting_evidence_pack? +

Yes. Add a rate_limit block to the carrier_vetting_evidence_pack 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 carrier_vetting_evidence_pack completely? +

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

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

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 294 Livedatalink tools →

Across the catalogue

generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →