This record as markdown: /tools/creativelead-unclick/convert-data-storage.md
What convert_data_storage does on UnClick
AI agents call convert_data_storage as a supporting operation in UnClick workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | |
from | string | — | |
value | number | — |
Parameters from the server's own tool schema.
Why convert_data_storage is rated Low
This tool performs a pure mathematical unit conversion (e.g., bytes to gigabytes) with no side effects, no data retrieval, no writes, and no external service interaction. It is a stateless utility function that genuinely falls outside Read/Write/Execute/Destructive/Financial categories.
From the tool's definition Convert between data storage units
Attacks that exploit this kind of access
The rule that runs convert_data_storage 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_data_storage, this is the rule to start with:
convert_data_storage gets a rate cap, and 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_data_storage call is checked against it from then on.
Questions about convert_data_storage
Convert between data storage units. It is categorised as a Other tool in the UnClick MCP Server, which means it performs auxiliary operations.
convert_data_storage accepts 3 parameters: 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_data_storage: 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_data_storage is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the convert_data_storage 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_data_storage. 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_data_storage is provided by the UnClick MCP server (creativelead/unclick). 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