file_size_humanize
File Size Humanizer — Format a byte count as a human-readable string using binary IEC prefixes (KiB/MiB/GiB) or decimal SI prefixes (KB/MB/GB).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/file-size-humanize.md
What file_size_humanize does on Gateway
AI agents call file_size_humanize 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 |
|---|---|---|---|
mode | string | — | binary | decimal (default binary) |
bytes | number | Yes | Byte count to format (>= 0) |
precision | integer | — | Decimal places above the base unit, 0-6 (default 2) |
Parameters from the server's own tool schema.
Why file_size_humanize is rated Low
This tool takes a numeric byte count as input and returns a formatted string representation. It performs no data retrieval, modification, deletion, code execution, or financial operations. It is a stateless utility function with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool name 'file_size_humanize' and description 'Format a byte count as a human-readable string' indicate a pure formatting/transformation utility that reads input and returns formatted output with no side effects.
Attacks that exploit this kind of access
The rule that runs file_size_humanize 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 file_size_humanize, this is the rule to start with:
file_size_humanize is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every file_size_humanize call is checked against it from then on.
Questions about file_size_humanize
File Size Humanizer — Format a byte count as a human-readable string using binary IEC prefixes (KiB/MiB/GiB) or decimal SI prefixes (KB/MB/GB). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
file_size_humanize accepts 3 parameters: mode, bytes, precision. Required: bytes. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for file_size_humanize: 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.
file_size_humanize is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the file_size_humanize 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 file_size_humanize. 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.
file_size_humanize 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.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue