iban.banking.calculate
Calculate a valid IBAN from domestic bank routing details: country code, bank code, account number, and optional branch code. Returns the computed IBAN with correct checksum. Useful for payment automation.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/iban.banking.calculate.md
What iban.banking.calculate does on Apibase
AI agents call iban.banking.calculate to retrieve information from Apibase 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 |
|---|---|---|---|
bank_code | string | Yes | Domestic bank code (e.g. "37040044" for Germany, "NWBK" for UK) |
branch_code | string | — | Branch/sort code if required by the country (e.g. "601613" for UK) |
country_code | string | Yes | ISO 3166-1 alpha-2 country code (e.g. "DE", "GB", "FR", "NL") |
account_number | string | Yes | Account number in domestic format |
Parameters from the server's own tool schema.
Why iban.banking.calculate is rated Low
Even though iban.banking.calculate only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs iban.banking.calculate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iban.banking.calculate, this is the rule to start with:
iban.banking.calculate 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 Apibase, apply this rule, and every iban.banking.calculate call is checked against it from then on.
Questions about iban.banking.calculate
Calculate a valid IBAN from domestic bank routing details: country code, bank code, account number, and optional branch code. Returns the computed IBAN with correct checksum. Useful for payment automation. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
iban.banking.calculate accepts 4 parameters: bank_code, branch_code, country_code, account_number. Required: bank_code, country_code, account_number. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for iban.banking.calculate: 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 Apibase. Nothing to install.
iban.banking.calculate 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 iban.banking.calculate 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 iban.banking.calculate. 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.
iban.banking.calculate is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue