checksum
Checksum Validator — Validate or compute check digits for IBAN, ISBN-10, and ISBN-13 identifiers.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/checksum.md
What checksum does on Gateway
AI agents call checksum 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 |
|---|---|---|---|
mode | string | — | validate or check_digit |
value | string | Yes | Value to check (spaces/dashes ignored) |
scheme | string | — | Checksum scheme |
Parameters from the server's own tool schema.
Why checksum is rated Low
Checksum computation and validation are pure computational functions that retrieve or derive data without modifying, deleting, or executing arbitrary operations. Even though IBAN involves financial identifiers, the tool only validates/computes checksums rather than moving money or making financial commitments. No irreversible changes, no code execution, no financial transactions.
From the tool's definition Tool description states it 'Validate or compute check digits' for financial and bibliographic identifiers (IBAN, ISBN).
Attacks that exploit this kind of access
The rule that runs checksum 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 checksum, this is the rule to start with:
checksum 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 checksum call is checked against it from then on.
Questions about checksum
Checksum Validator — Validate or compute check digits for IBAN, ISBN-10, and ISBN-13 identifiers. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
checksum accepts 3 parameters: mode, value, scheme. Required: value. 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 checksum: 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.
checksum 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 checksum 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 checksum. 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.
checksum 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