compute_vat
PAID ($0.02). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if y...
This record as markdown: /tools/dev-asiaref-reference-data/compute-vat.md
What compute_vat does on Reference Data
AI agents use compute_vat to create or update resources in Reference Data, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reference Data environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | add = amount is net (default); extract = amount is gross |
amount | number | Yes | Amount in the country's own currency |
api_key | string | — | API key |
country | string | Yes | ISO country code |
Parameters from the server's own tool schema.
Why compute_vat is rated Medium
An AI agent can call compute_vat faster than any human can review: one bad instruction and it creates or modifies resources in Reference Data by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs compute_vat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Reference Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compute_vat, this is the rule to start with:
compute_vat stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Reference Data, apply this rule, and every compute_vat call is checked against it from then on.
Questions about compute_vat
PAID ($0.02). VAT breakdown for an amount: net, tax and gross using the country's current statutory rate, including per-levy components where the rate is composite (e.g. Ghana VAT + NHIL + GETFund). mode=add treats the amount as net; mode=extract backs VAT out of a gross amount. Pass api_key if you have one; otherwise the response explains how to pay via x402. It is categorised as a Write tool in the Reference Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
compute_vat accepts 4 parameters: mode, amount, api_key, country. Required: amount, country. The full parameter table on this page comes from the server's own tool schema.
Register the Reference Data MCP server in PolicyLayer and add a rule for compute_vat: 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 Reference Data. Nothing to install.
compute_vat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compute_vat 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 compute_vat. 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.
compute_vat is provided by the Reference Data MCP server (https://asiaref.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Reference Data, and thousands of servers like it.
This server
Across the catalogue