tax.vatcomply.validate
Validate a European VAT number via VIES — returns validity status, company name, and registered address. Supports all 27 EU member states + UK. Format: country prefix + number (e.g. DE123456789) (VATcomply, open source)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tax.vatcomply.validate.md
What tax.vatcomply.validate does on Apibase
AI agents call tax.vatcomply.validate 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 |
|---|---|---|---|
vat_number | string | Yes | EU VAT number with country prefix (e.g. "DE123456789", "FR12345678901", "GB123456789") |
Parameters from the server's own tool schema.
Why tax.vatcomply.validate is rated Low
Tool queries external VAT database for read-only information retrieval with no data modification or destructive capability.
From the tool's definition Validate a European VAT number via VIES — returns validity status, company name, and registered address.
Attacks that exploit this kind of access
The rule that runs tax.vatcomply.validate 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.validate, this is the rule to start with:
tax.vatcomply.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 Apibase, apply this rule, and every tax.vatcomply.validate call is checked against it from then on.
Questions about tax.vatcomply.validate
Validate a European VAT number via VIES — returns validity status, company name, and registered address. Supports all 27 EU member states + UK. Format: country prefix + number (e.g. DE123456789) (VATcomply, open source). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
tax.vatcomply.validate accepts 1 parameter: vat_number. Required: vat_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 tax.vatcomply.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 Apibase. Nothing to install.
tax.vatcomply.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 tax.vatcomply.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 tax.vatcomply.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.
tax.vatcomply.validate 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