tariff_impact_simulator
As a COO, model how proposed tariff changes affect landed costs for imported goods. Inputs: HS code, current tariff rate, proposed tariff rate, product value, shipping cost, and country of origin. Outputs: detailed cost breakdown including new duties, taxes, and total landed cost impact. Sources ...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/tariff-impact-simulator.md
What tariff_impact_simulator does on Mcp Knowledge
AI agents call tariff_impact_simulator 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 |
|---|---|---|---|
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 |
hsCode | string | Yes | |
productValue | number | Yes | |
shippingCost | number | — | |
countryOfOrigin | string | Yes | |
currentTariffRate | number | Yes | |
proposedTariffRate | number | Yes |
Parameters from the server's own tool schema.
Why tariff_impact_simulator is rated Low
The tool performs tariff impact modeling and cost simulation using WTO and US Census trade data. It takes inputs (HS code, rates, values) and outputs a cost breakdown. There are no side effects — no money moves, no data is written, no commands are executed. It is purely analytical/read-oriented, drawing on external reference data to compute landed cost scenarios.
From the tool's definition 'model how proposed tariff changes affect landed costs' and 'Outputs: detailed cost breakdown including new duties, taxes, and total landed cost impact' — this is a simulation/calculation tool that reads trade data and models scenarios
Attacks that exploit this kind of access
The rule that runs tariff_impact_simulator 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 tariff_impact_simulator, this is the rule to start with:
tariff_impact_simulator 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 tariff_impact_simulator call is checked against it from then on.
Questions about tariff_impact_simulator
As a COO, model how proposed tariff changes affect landed costs for imported goods. Inputs: HS code, current tariff rate, proposed tariff rate, product value, shipping cost, and country of origin. Outputs: detailed cost breakdown including new duties, taxes, and total landed cost impact. Sources include WTO TFA and US Census trade data. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
tariff_impact_simulator accepts 7 parameters: async, hsCode, productValue, shippingCost, countryOfOrigin, currentTariffRate, proposedTariffRate. Required: hsCode, productValue, countryOfOrigin, currentTariffRate, proposedTariffRate. 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 tariff_impact_simulator: 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.
tariff_impact_simulator 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 tariff_impact_simulator 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 tariff_impact_simulator. 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.
tariff_impact_simulator 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