vehicle_recalls
Check for safety recalls on a vehicle by year, make, and model. Returns all NHTSA recall campaigns including affected component, description, safety risk, and recommended remedy. Use this for 'are there recalls on my car?', 'check recalls for 2020 Toyota Camry', 'is this vehicle safe?', 'any open...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/vehicle-recalls.md
What vehicle_recalls does on Livedatalink
AI agents call vehicle_recalls to retrieve information from Livedatalink 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', 'Ford') |
year | integer | Yes | Model year (e.g., 2020) |
model | string | Yes | Vehicle model (e.g., 'Camry', 'F-150') |
Parameters from the server's own tool schema.
Why vehicle_recalls is rated Low
This tool retrieves public safety recall information without any side effects. It does not create, modify, delete, or execute anything — it simply queries and returns existing recall data. This is a straightforward read operation with minimal security risk. The data returned is public safety information intended for consumer awareness.
From the tool's definition Tool description states 'Check for safety recalls' and 'Returns all NHTSA recall campaigns' — these are query/retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs vehicle_recalls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vehicle_recalls, this is the rule to start with:
vehicle_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 Livedatalink, apply this rule, and every vehicle_recalls call is checked against it from then on.
Questions about vehicle_recalls
Check for safety recalls on a vehicle by year, make, and model. Returns all NHTSA recall campaigns including affected component, description, safety risk, and recommended remedy. Use this for 'are there recalls on my car?', 'check recalls for 2020 Toyota Camry', 'is this vehicle safe?', 'any open recalls?', or any vehicle recall check. Covers all US vehicles from all manufacturers. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
vehicle_recalls accepts 3 parameters: make, year, model. Required: make, year, model. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for vehicle_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 Livedatalink. Nothing to install.
vehicle_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 vehicle_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 vehicle_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.
vehicle_recalls is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue