vin_check_digit
VIN Check Digit Validator — Validate a 17-character VIN's ISO 3779/NHTSA check digit (position 9), or compute the check digit a partial VIN would need.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/vin-check-digit.md
What vin_check_digit does on Gateway
AI agents call vin_check_digit to retrieve information from Gateway 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 |
|---|---|---|---|
vin | string | Yes | 17-character VIN |
mode | string | — | validate | check_digit (default validate) |
Parameters from the server's own tool schema.
Why vin_check_digit is rated Low
The VIN check digit validator is purely computational—it validates existing VINs against ISO 3779 standards or derives what a check digit should be. No data is created, modified, deleted, or irreversibly changed. No external operations, code execution, or financial transactions occur. This is a query/lookup operation with zero blast radius.
From the tool's definition Tool description states it 'Validate[s] a 17-character VIN's ISO 3779/NHTSA check digit' or 'compute[s] the check digit'.
Attacks that exploit this kind of access
The rule that runs vin_check_digit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vin_check_digit, this is the rule to start with:
vin_check_digit 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 Gateway, apply this rule, and every vin_check_digit call is checked against it from then on.
Questions about vin_check_digit
VIN Check Digit Validator — Validate a 17-character VIN's ISO 3779/NHTSA check digit (position 9), or compute the check digit a partial VIN would need. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
vin_check_digit accepts 2 parameters: vin, mode. Required: vin. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for vin_check_digit: 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 Gateway. Nothing to install.
vin_check_digit 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 vin_check_digit 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 vin_check_digit. 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.
vin_check_digit is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue