fmcsa_safety_scores
Get safety information for a trucking company by DOT number. Returns either CSA BASIC percentile scores (where FMCSA publishes them, rare per FAST Act 2015 restrictions) OR a public safety summary built from crash counts, fatal/injury crashes, driver/vehicle/hazmat out-of-service rates, and inspe...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fmcsa-safety-scores.md
What fmcsa_safety_scores does on Livedatalink
AI agents call fmcsa_safety_scores 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 |
|---|---|---|---|
dot_number | integer | Yes |
Parameters from the server's own tool schema.
Why fmcsa_safety_scores is rated Low
This tool retrieves and queries publicly available safety data for trucking companies by DOT number. It has no side effects, does not create, modify, delete, or execute operations. The data returned (safety scores, crash counts, inspection history) is informational only. The use cases cited are all read-only evaluations. Misuse would have minimal impact as the tool only exposes factual public safety records.
From the tool's definition Tool description indicates 'Get safety information' and 'Returns...safety summary built from crash counts, fatal/injury crashes, driver/vehicle/hazmat out-of-service rates, and inspection volumes.' The verb 'Get' and 'Returns' indicate data retrieval with no…
Attacks that exploit this kind of access
The rule that runs fmcsa_safety_scores 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 fmcsa_safety_scores, this is the rule to start with:
fmcsa_safety_scores 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 fmcsa_safety_scores call is checked against it from then on.
Questions about fmcsa_safety_scores
Get safety information for a trucking company by DOT number. Returns either CSA BASIC percentile scores (where FMCSA publishes them, rare per FAST Act 2015 restrictions) OR a public safety summary built from crash counts, fatal/injury crashes, driver/vehicle/hazmat out-of-service rates, and inspection volumes (always available). Use this for questions like 'is this carrier safe?', 'what's their safety record?', 'how many crashes?', 'should I hire this carrier?', 'check their inspection history', or any trucking safety evaluation. Higher BASIC percentiles = worse record. For OOS rates, lower is better; national averages provided for comparison. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fmcsa_safety_scores accepts 1 parameter: dot_number. Required: dot_number. 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 fmcsa_safety_scores: 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.
fmcsa_safety_scores 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 fmcsa_safety_scores 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 fmcsa_safety_scores. 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.
fmcsa_safety_scores 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