tax_compliance_multi
Multi-jurisdiction tax compliance data for international SaaS, cross-border marketplaces and expat services. Five modes: (1) vat_lookup — validate EU VAT numbers live via VIES SOAP (27 EU countries) or UK VRN via HMRC; (2) sales_tax — US state sales tax rates, nexus thresholds (post-Wayfair 2018)...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/tax-compliance-multi.md
What tax_compliance_multi does on Mcp Knowledge
AI agents call tax_compliance_multi to retrieve information from Mcp Knowledge 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 | Yes | Tax mode to invoke. |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
query | string | Yes | Mode-specific query: vat_lookup -> VAT number with country prefix (e.g. 'FR40303265045'); sales_tax -> US state code or name (e.g. 'CA', 'California'); gst -> I |
country | string | — | ISO 3166-1 alpha-2 country code. Required for gst when query is ambiguous. Used in transfer_pricing_benchmark for country-specific OECD adjustments. |
transaction_type | string | — | Transaction type for signal generation. 'digital' triggers GST/sales-tax digital goods warnings. |
Parameters from the server's own tool schema.
Why tax_compliance_multi is rated Low
The tool retrieves tax rates, validates VAT numbers, and performs eligibility analysis. All described modes are read/query operations with no indication of writing, executing code, or moving money. Severity is medium because misuse could provide incorrect tax compliance guidance affecting financial decisions, but no direct financial transactions occur.
From the tool's definition 'Multi-jurisdiction tax compliance data', 'validate EU VAT numbers live via VIES SOAP', 'US state sales tax rates', 'GST/SST/consumption-tax rates', 'OSS/IOSS eligibility analysis' — all retrieval and lookup operations
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs tax_compliance_multi safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tax_compliance_multi, this is the rule to start with:
tax_compliance_multi 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 Mcp Knowledge, apply this rule, and every tax_compliance_multi call is checked against it from then on.
Questions about tax_compliance_multi
Multi-jurisdiction tax compliance data for international SaaS, cross-border marketplaces and expat services. Five modes: (1) vat_lookup — validate EU VAT numbers live via VIES SOAP (27 EU countries) or UK VRN via HMRC; (2) sales_tax — US state sales tax rates, nexus thresholds (post-Wayfair 2018), digital goods taxability for all 50 states + DC; (3) gst — APAC GST/SST/consumption-tax rates for IN, SG, AU, NZ, MY, JP, KR, TH, ID, PH, VN with reduced rates and registration thresholds; (4) oss_ioss_eligibility — EU One-Stop-Shop and Import-OSS eligibility analysis (EUR 10k OSS threshold, EUR 150 IOSS per-consignment); (5) transfer_pricing_benchmark — OECD/JTPF operating-margin benchmarks by industry and country (20+ sectors, country-specific adjustments). Returns P0/P1/P2 compliance signals: P0=invalid VAT used for zero-rating, P1=taxable digital goods detected/audit risk, P2=filing deadlines/nexus alerts. Keyless — no API key required. Optional env: HMRC_VAT_API_KEY for UK VAT live validation. Cache TTL 24h. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
tax_compliance_multi accepts 5 parameters: mode, async, query, country, transaction_type. Required: mode, query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for tax_compliance_multi: 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 Mcp Knowledge. Nothing to install.
tax_compliance_multi 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_compliance_multi 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_compliance_multi. 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_compliance_multi is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue