util_unit_convert
Convert values between units (length, mass, volume, time, data, temperature). Supports one conversion or a batch of up to 100.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-unit-convert.md
What util_unit_convert does on Delx Protocol — Agent Recovery & Continuity
AI agents use util_unit_convert to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
value | number | — | Single value to convert (or use conversions[]) |
to_unit | string | — | Target unit, e.g. mi, kg, f, gib |
from_unit | string | — | Source unit, e.g. km, lb, c, mib |
conversions | array | — | Optional batch of {value, from_unit, to_unit} (max 100) |
Parameters from the server's own tool schema.
Why util_unit_convert is rated Medium
An AI agent can call util_unit_convert faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs util_unit_convert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_unit_convert, this is the rule to start with:
util_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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_unit_convert call is checked against it from then on.
Questions about util_unit_convert
Convert values between units (length, mass, volume, time, data, temperature). Supports one conversion or a batch of up to 100. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
util_unit_convert accepts 4 parameters: value, to_unit, from_unit, conversions. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
util_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 util_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 util_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.
util_unit_convert is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue