This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/convert-volume.md
What convert_volume does on UnClick
AI agents use convert_volume to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | |
from | string | Yes | |
value | number | Yes |
Parameters from the server's own tool schema.
Why convert_volume is rated Medium
An AI agent can call convert_volume faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs convert_volume safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convert_volume, this is the rule to start with:
convert_volume 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 UnClick, apply this rule, and every convert_volume call is checked against it from then on.
Questions about convert_volume
Convert between volume units. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
convert_volume accepts 3 parameters: to, from, value. Required: to, from, value. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for convert_volume: 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 UnClick. Nothing to install.
convert_volume 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 convert_volume 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 convert_volume. 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.
convert_volume is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue