tax.vatcomply.currencies
Current ECB reference exchange rates for 30+ currencies (USD, GBP, JPY, CHF, etc.) plus currency metadata — symbol, decimal places, issuing countries (VATcomply / ECB)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tax.vatcomply.currencies.md
What tax.vatcomply.currencies does on Apibase
AI agents call tax.vatcomply.currencies 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 |
|---|---|---|---|
filter | string | — | Optional currency code filter (e.g. "USD", "GBP"). Omit for all currencies |
Parameters from the server's own tool schema.
Why tax.vatcomply.currencies is rated Low
Fetches read-only financial data with no side effects or ability to modify state.
From the tool's definition retrieves current ECB reference exchange rates and currency metadata
Attacks that exploit this kind of access
The rule that runs tax.vatcomply.currencies 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 tax.vatcomply.currencies, this is the rule to start with:
tax.vatcomply.currencies 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 tax.vatcomply.currencies call is checked against it from then on.
Questions about tax.vatcomply.currencies
Current ECB reference exchange rates for 30+ currencies (USD, GBP, JPY, CHF, etc.) plus currency metadata — symbol, decimal places, issuing countries (VATcomply / ECB). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
tax.vatcomply.currencies accepts 1 parameter: filter. 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 tax.vatcomply.currencies: 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.
tax.vatcomply.currencies 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 tax.vatcomply.currencies 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 tax.vatcomply.currencies. 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.
tax.vatcomply.currencies 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