routing_number
Bank Routing Number Validator — Validate a US ABA bank routing number's checksum, or compute the check digit for an 8-digit partial. Complements the checksum tool (IBAN/ISBN), which doesn't cover this scheme.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/routing-number.md
What routing_number does on Gateway
AI agents call routing_number 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 | check_digit (default validate) |
number | string | Yes | Routing number (9 digits to validate, or 8 digits for check_digit) |
Parameters from the server's own tool schema.
Why routing_number is rated Low
The routing_number tool performs checksum validation and check digit computation on bank routing numbers. These are read-only, deterministic mathematical operations that retrieve or derive information without creating, modifying, deleting, or triggering external side effects.
From the tool's definition Tool description states 'Validate' and 'compute' for bank routing numbers—purely computational validation tasks with no state changes, data modification, or external operations.
Attacks that exploit this kind of access
The rule that runs routing_number 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 routing_number, this is the rule to start with:
routing_number 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 routing_number call is checked against it from then on.
Questions about routing_number
Bank Routing Number Validator — Validate a US ABA bank routing number's checksum, or compute the check digit for an 8-digit partial. Complements the checksum tool (IBAN/ISBN), which doesn't cover this scheme. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
routing_number accepts 2 parameters: mode, number. Required: number. 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 routing_number: 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.
routing_number 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 routing_number 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 routing_number. 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.
routing_number 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