load_tender_fraud_shield
Screen a carrier before accepting or dispatching a load. Resolves the carrier and combines FMCSA authority, insurance, safety, sanctions, court, and federal-award evidence with the supplied tender context. Flags inactive authority, missing liability evidence, sanctions or litigation findings, bro...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/load-tender-fraud-shield.md
What load_tender_fraud_shield does on Livedatalink
AI agents call load_tender_fraud_shield 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 | string | — | MC/MX number. Accepts 123456 or MC-123456. |
dot | number | string | — | USDOT number (preferred). Accepts 3405079 or USDOT 3405079. |
name | string | — | Carrier legal name when DOT/MC is unavailable. |
format | string | — | Report format. Defaults to markdown. |
load_id | string | — | Optional internal load/tender identifier to echo in the report. |
carrier_address | string | — | Address supplied with the tender or onboarding packet, used for a coarse location consistency check. |
Parameters from the server's own tool schema.
Why load_tender_fraud_shield is rated Low
Even though load_tender_fraud_shield 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 load_tender_fraud_shield 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 load_tender_fraud_shield, this is the rule to start with:
load_tender_fraud_shield 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 load_tender_fraud_shield call is checked against it from then on.
Questions about load_tender_fraud_shield
Screen a carrier before accepting or dispatching a load. Resolves the carrier and combines FMCSA authority, insurance, safety, sanctions, court, and federal-award evidence with the supplied tender context. Flags inactive authority, missing liability evidence, sanctions or litigation findings, broker-only records, and mismatches between the carrier's reported location and the tender contact address. Returns CLEAR, REVIEW, or BLOCK with reasons, source coverage, primary links, and a dispatcher verification checklist. This is an analytical fraud-screening aid, not a substitute for direct FMCSA or insurance verification. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
load_tender_fraud_shield accepts 6 parameters: mc, dot, name, format, load_id, carrier_address. 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 load_tender_fraud_shield: 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.
load_tender_fraud_shield 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 load_tender_fraud_shield 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 load_tender_fraud_shield. 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.
load_tender_fraud_shield 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