vehicle.safety.complaints
Search consumer complaints filed with NHTSA about vehicles. Returns incident details including crash/fire flags, injuries, deaths, affected components, and complaint summary. Covers US vehicles from ~1995 to present. Critical for safety research and product liability analysis (NHTSA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/vehicle.safety.complaints.md
What vehicle.safety.complaints does on Apibase
AI agents call vehicle.safety.complaints 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 | Yes | Vehicle manufacturer name (e.g. "Toyota", "Ford", "Tesla", "Honda") |
model | string | Yes | Vehicle model name (e.g. "Camry", "Model 3", "Civic") |
model_year | integer | Yes | Model year (e.g. 2023). NHTSA complaint data available from ~1995 to present |
Parameters from the server's own tool schema.
Why vehicle.safety.complaints is rated Low
Tool retrieves historical safety complaint data without modification, deletion, or execution capabilities.
From the tool's definition Search consumer complaints filed with NHTSA about vehicles. Returns incident details.
Attacks that exploit this kind of access
The rule that runs vehicle.safety.complaints 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.complaints, this is the rule to start with:
vehicle.safety.complaints 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.complaints call is checked against it from then on.
Questions about vehicle.safety.complaints
Search consumer complaints filed with NHTSA about vehicles. Returns incident details including crash/fire flags, injuries, deaths, affected components, and complaint summary. Covers US vehicles from ~1995 to present. Critical for safety research and product liability analysis (NHTSA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
vehicle.safety.complaints accepts 3 parameters: make, model, model_year. Required: make, model, model_year. 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.complaints: 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.complaints 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.complaints 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.complaints. 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.complaints 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