unit_convert
Unit conversion across 14 categories with exact defined factors: length, mass, volume (US and imperial), area, speed, time, data (SI kB vs IEC KiB, bits vs bytes), pressure, energy, power, angle, frequency, temperature (C, F, K, Rankine) and fuel economy (mpg US/UK, L/100 km, km/L). Common names ...
This record as markdown: /tools/com-it-scorptech-x402/unit-convert.md
What unit_convert does on ScorpTech x402 API
AI agents use unit_convert to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | Target unit (omit with all=true) |
all | boolean | — | Also return the value in every unit of the category |
from | string | Yes | Source unit, e.g. mi, kg, F, GiB, psi, mpg |
value | number | Yes | Quantity to convert |
precision | integer | — | Significant digits in the output |
Parameters from the server's own tool schema.
Why unit_convert is rated Medium
An AI agent can call unit_convert faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs unit_convert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unit_convert, this is the rule to start with:
unit_convert 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 ScorpTech x402 API, apply this rule, and every unit_convert call is checked against it from then on.
Questions about unit_convert
Unit conversion across 14 categories with exact defined factors: length, mass, volume (US and imperial), area, speed, time, data (SI kB vs IEC KiB, bits vs bytes), pressure, energy, power, angle, frequency, temperature (C, F, K, Rankine) and fuel economy (mpg US/UK, L/100 km, km/L). Common names and abbreviations accepted; optionally lists the value in every unit of the category. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/unit-convert. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unit_convert accepts 5 parameters: to, all, from, value, precision. Required: from, value. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for unit_convert: 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 ScorpTech x402 API. Nothing to install.
unit_convert 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 unit_convert 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 unit_convert. 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.
unit_convert is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue