luhn_validate
Validate or generate a Luhn check digit (credit cards, IMEI, etc.).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/luhn-validate.md
What luhn_validate does on UnClick
AI agents call luhn_validate 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 |
|---|---|---|---|
mode | string | — | 'validate' (default) or 'generate' to compute check digit. |
number | string | Yes | Digit string to validate or partial number for generation. |
Parameters from the server's own tool schema.
Why luhn_validate is rated Low
Luhn validation is a checksum algorithm used to verify the mathematical validity of numbers like credit card or IMEI identifiers. The tool performs pure computation: it either validates an existing check digit or generates one for demonstration/testing purposes. This is a read-like operation with no capability to modify data, execute commands, delete records, or commit financial transactions.
From the tool's definition Tool description states 'Validate or generate a Luhn check digit' — a mathematical validation/generation function with no side effects, no data modification, and no external operations triggered.
Attacks that exploit this kind of access
The rule that runs luhn_validate 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 luhn_validate, this is the rule to start with:
luhn_validate 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 luhn_validate call is checked against it from then on.
Questions about luhn_validate
Validate or generate a Luhn check digit (credit cards, IMEI, etc.). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
luhn_validate accepts 2 parameters: mode, number. Required: number. 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 luhn_validate: 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.
luhn_validate 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 luhn_validate 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 luhn_validate. 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.
luhn_validate 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