gov.carrier-safety
FMCSA motor-carrier (trucking/bus) safety profile. Pass dot (USDOT number) for the full record: legal/DBA name, state, interstate/intrastate, operating-authority status (allowedToOperate), FMCSA safety rating, fleet size, crash history (total/fatal/injury/tow-away), roadside-inspection history wi...
This record as markdown: /tools/io-github-2s-io-mcp/gov.carrier-safety.md
What gov.carrier-safety does on Mcp
AI agents call gov.carrier-safety to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gov.carrier-safety is rated Low
This is a straightforward data retrieval tool that queries and returns structured safety profile information. It has no side effects, does not execute code or commands, does not modify or delete data, and involves no financial transactions. The tool is purely informational and read-only in nature.
From the tool's definition Tool queries FMCSA motor-carrier safety profiles by passing a DOT number to retrieve 'legal/DBA name, state, interstate/intrastate, operating-authority status, safety rating, fleet size, crash history, roadside-inspection history, CSA BASIC measures' or…
Attacks that exploit this kind of access
The rule that runs gov.carrier-safety safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gov.carrier-safety, this is the rule to start with:
gov.carrier-safety 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 Mcp, apply this rule, and every gov.carrier-safety call is checked against it from then on.
Questions about gov.carrier-safety
FMCSA motor-carrier (trucking/bus) safety profile. Pass dot (USDOT number) for the full record: legal/DBA name, state, interstate/intrastate, operating-authority status (allowedToOperate), FMCSA safety rating, fleet size, crash history (total/fatal/injury/tow-away), roadside-inspection history with driver+vehicle out-of-service rates, and CSA BASIC measures (Unsafe Driving, Hours-of-Service, Driver Fitness, Controlled Substances, Vehicle Maintenance, Hazmat, Crash Indicator). Or pass name to search → matching carriers + DOT numbers. Free, public-domain US DOT data. For commercial-auto/freight underwriting, broker/shipper vetting, vendor diligence. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for gov.carrier-safety: 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 Mcp. Nothing to install.
gov.carrier-safety 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 gov.carrier-safety 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 gov.carrier-safety. 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.
gov.carrier-safety is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue