unit_convert

Unit Converter — Convert length, mass, volume, time, data or temperature between units.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 33 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/unit-convert.md

WHAT IT DOES

What unit_convert does on Gateway

AI agents call unit_convert to retrieve information from Gateway 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
`value`	number	Yes	Value to convert
`to_unit`	string	Yes	Target unit in the same category
`from_unit`	string	Yes	Source unit (e.g. km, lb, gal, C, MB)

Parameters from the server's own tool schema.

RISK

Why unit_convert is rated Low

This tool performs pure mathematical unit conversion calculations with no side effects, data storage, or external operations. It reads input values and returns converted output, making it a read/compute operation with minimal blast radius.

From the tool's definition Convert length, mass, volume, time, data or temperature between units

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs unit_convert safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, 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 Allowed

unit_convert is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unit_convert": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every unit_convert call is checked against it from then on.

FAQ

Questions about unit_convert

What does the unit_convert tool do? +

Unit Converter — Convert length, mass, volume, time, data or temperature between units. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does unit_convert accept? +

unit_convert accepts 3 parameters: value, to_unit, from_unit. Required: value, to_unit, from_unit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on unit_convert? +

Register the Gateway 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 Gateway. Nothing to install.

What risk level is unit_convert? +

unit_convert is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit unit_convert? +

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.

How do I block unit_convert completely? +

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.

What MCP server provides unit_convert? +

unit_convert is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →