vehicle.safety.ratings
Get NCAP 5-Star crash test safety ratings by make/model/year or vehicle ID. Returns overall rating, frontal crash, side crash, and rollover ratings (1-5 stars). Also shows related complaints, recalls, and investigation counts. Available from ~2011 for US-market vehicles (NHTSA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/vehicle.safety.ratings.md
What vehicle.safety.ratings does on Apibase
AI agents call vehicle.safety.ratings to retrieve information from Apibase 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 |
|---|---|---|---|
make | string | — | Vehicle manufacturer name (e.g. "Toyota", "Honda"). Required unless vehicle_id is provided |
model | string | — | Vehicle model name (e.g. "Camry", "Civic"). Required unless vehicle_id is provided |
model_year | integer | — | Model year (e.g. 2023). 5-Star ratings available from ~2011. Required unless vehicle_id is provided |
vehicle_id | integer | — | NHTSA Vehicle ID for full ratings detail (get from initial search). Overrides make/model/year if provided |
Parameters from the server's own tool schema.
Why vehicle.safety.ratings is rated Low
Tool retrieves vehicle safety data from NHTSA with no data modification, creation, or side effects.
From the tool's definition Get NCAP 5-Star crash test safety ratings, returns rating data, complaints, recalls, investigation counts.
Attacks that exploit this kind of access
The rule that runs vehicle.safety.ratings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vehicle.safety.ratings, this is the rule to start with:
vehicle.safety.ratings 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 Apibase, apply this rule, and every vehicle.safety.ratings call is checked against it from then on.
Questions about vehicle.safety.ratings
Get NCAP 5-Star crash test safety ratings by make/model/year or vehicle ID. Returns overall rating, frontal crash, side crash, and rollover ratings (1-5 stars). Also shows related complaints, recalls, and investigation counts. Available from ~2011 for US-market vehicles (NHTSA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
vehicle.safety.ratings accepts 4 parameters: make, model, model_year, vehicle_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for vehicle.safety.ratings: 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 Apibase. Nothing to install.
vehicle.safety.ratings 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 vehicle.safety.ratings 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 vehicle.safety.ratings. 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.
vehicle.safety.ratings is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue