vehicle.recalls

NHTSA vehicle recall lookup. Search by VIN (precise), or make/model/year, or NHTSA campaign ID. Returns recall ID, component, summary, consequence, remedy, dates.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/vehicle.recalls.md

WHAT IT DOES

What vehicle.recalls does on Mcp

AI agents call vehicle.recalls to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why vehicle.recalls is rated Low

This is a lookup/search tool that queries publicly available NHTSA recall information and returns results. It has no side effects, does not modify data, execute code, delete records, or handle financial transactions. The pay-per-call settlement mechanism on the MCP server is a billing artifact, not a function of this specific tool.

From the tool's definition Tool description states it 'Search[es] by VIN...or make/model/year, or NHTSA campaign ID. Returns recall ID, component, summary, consequence, remedy, dates.' — purely retrieves and returns data from NHTSA vehicle recall database with no modification,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vehicle.recalls safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, 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 Allowed

vehicle.recalls is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vehicle.recalls": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every vehicle.recalls call is checked against it from then on.

FAQ

Questions about vehicle.recalls

What does the vehicle.recalls tool do? +

NHTSA vehicle recall lookup. Search by VIN (precise), or make/model/year, or NHTSA campaign ID. Returns recall ID, component, summary, consequence, remedy, dates. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vehicle.recalls? +

Register the 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 Mcp. Nothing to install.

What risk level is vehicle.recalls? +

vehicle.recalls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vehicle.recalls? +

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.

How do I block vehicle.recalls completely? +

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.

What MCP server provides vehicle.recalls? +

vehicle.recalls is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →