carrier_monitor_recheck
Recheck an existing carrier snapshot and identify meaningful changes since the previous check. Accepts a DOT/MC/name plus the prior result or snapshot as previous_snapshot, then compares authority, identity, insurance summary, BASIC alerts, crashes, out-of-service indicators, safety rating, and v...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/carrier-monitor-recheck.md
What carrier_monitor_recheck does on Livedatalink
AI agents call carrier_monitor_recheck 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. |
previous_snapshot | object | — | Prior carrier_vetting result or JSON snapshot returned by an earlier call. |
Parameters from the server's own tool schema.
Why carrier_monitor_recheck is rated Low
Even though carrier_monitor_recheck 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_monitor_recheck 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_monitor_recheck, this is the rule to start with:
carrier_monitor_recheck 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_monitor_recheck call is checked against it from then on.
Questions about carrier_monitor_recheck
Recheck an existing carrier snapshot and identify meaningful changes since the previous check. Accepts a DOT/MC/name plus the prior result or snapshot as previous_snapshot, then compares authority, identity, insurance summary, BASIC alerts, crashes, out-of-service indicators, safety rating, and verdict. Returns unchanged/changed status, a severity, field-level changes, and the next reviewer action. Store the returned current_snapshot in your own system and call this on a schedule; LiveDataLink does not silently retain customer watchlists. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
carrier_monitor_recheck accepts 5 parameters: mc, dot, name, format, previous_snapshot. 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_monitor_recheck: 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_monitor_recheck 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_monitor_recheck 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_monitor_recheck. 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_monitor_recheck 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