nhtsa_recalls
Search NHTSA vehicle safety recalls by make, model, and year.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/nhtsa-recalls.md
What nhtsa_recalls does on UnClick
AI agents call nhtsa_recalls to retrieve information from UnClick 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 make (e.g. Toyota). |
year | string | Yes | Model year (e.g. 2020). |
model | string | — | Vehicle model (e.g. Camry). |
Parameters from the server's own tool schema.
Why nhtsa_recalls is rated Low
This is a straightforward data retrieval tool that searches a public safety database for vehicle recall information. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions. The query returns factual recall information based on search parameters (make, model, year).
From the tool's definition Tool name 'nhtsa_recalls' and description 'Search NHTSA vehicle safety recalls' indicate a query operation that retrieves data from the National Highway Traffic Safety Administration database without modifying, executing, or destructively affecting any system.
Attacks that exploit this kind of access
The rule that runs nhtsa_recalls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nhtsa_recalls, this is the rule to start with:
nhtsa_recalls 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 UnClick, apply this rule, and every nhtsa_recalls call is checked against it from then on.
Questions about nhtsa_recalls
Search NHTSA vehicle safety recalls by make, model, and year. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
nhtsa_recalls accepts 3 parameters: make, year, model. Required: make, year. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for nhtsa_recalls: 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 UnClick. Nothing to install.
nhtsa_recalls 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 nhtsa_recalls 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 nhtsa_recalls. 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.
nhtsa_recalls is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue