vehicle.safety.investigations
Search NHTSA defect investigation records by manufacturer and model. Returns investigation number, type (preliminary/engineering analysis), description, latest activity date, and NHTSA action number. Covers active and closed investigations for US vehicles (NHTSA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/vehicle.safety.investigations.md
What vehicle.safety.investigations does on Apibase
AI agents call vehicle.safety.investigations 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. "Tesla", "GM", "Ford") |
model | string | — | Vehicle model name to narrow results (e.g. "Model 3", "Bolt EV") |
Parameters from the server's own tool schema.
Why vehicle.safety.investigations is rated Low
Queries public NHTSA safety investigation data with no modification, deletion, or execution capability.
From the tool's definition Search NHTSA defect investigation records by manufacturer, model. Returns investigation number, type, description, date.
Attacks that exploit this kind of access
The rule that runs vehicle.safety.investigations 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.investigations, this is the rule to start with:
vehicle.safety.investigations 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.investigations call is checked against it from then on.
Questions about vehicle.safety.investigations
Search NHTSA defect investigation records by manufacturer and model. Returns investigation number, type (preliminary/engineering analysis), description, latest activity date, and NHTSA action number. Covers active and closed investigations for US vehicles (NHTSA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
vehicle.safety.investigations accepts 2 parameters: make, model. Required: make. 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.investigations: 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.investigations 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.investigations 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.investigations. 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.investigations 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