New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

carrier_vetting_evidence_pack

Produce a dated public-carrier evidence record for a human reviewer. Prefer an exact USDOT; existing MC and name inputs remain supported, with name matches requiring manual identity confirmation. Returns allowlisted FMCSA facts, explicit missing/unavailable source states, field dates separate fro...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee 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 carrier_vetting_evidence_pack does on Livedatalink

AI agents call carrier_vetting_evidence_pack 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.

ParameterTypeRequiredDescription
mc integer — MC/MX number without the prefix.
dot integer — USDOT number (preferred exact identifier).
name string — Legal carrier name when DOT/MC is unavailable.
format string — Record export format; HTML is a standalone printable document, not a hosted link.

Parameters from the server's own tool schema.

Why carrier_vetting_evidence_pack is rated Low

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

Questions about carrier_vetting_evidence_pack

What does the carrier_vetting_evidence_pack tool do? +

Produce a dated public-carrier evidence record for a human reviewer. Prefer an exact USDOT; existing MC and name inputs remain supported, with name matches requiring manual identity confirmation. Returns allowlisted FMCSA facts, explicit missing/unavailable source states, field dates separate from retrieval time, deterministic official source links, and separate human follow-up tasks. Export markdown (default), JSON, or printable HTML. No safety/booking verdict or verified-insurance claim; unavailable data is never a clean result. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does carrier_vetting_evidence_pack accept? +

carrier_vetting_evidence_pack accepts 4 parameters: mc, dot, name, format. 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 Read tool with low risk. Read-only tools are generally safe to allow by default.

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.

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.