bytes_to_human
Convert bytes to human-readable format.
This record as markdown: /tools/io-tinyfn-tinyfn/bytes-to-human.md
What bytes_to_human does on TinyFn
AI agents call bytes_to_human to retrieve information from TinyFn 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 |
|---|---|---|---|
bytes_val | integer | Yes | Size in bytes |
Parameters from the server's own tool schema.
Why bytes_to_human is rated Low
This is a pure transformation utility that reads input (a byte value) and outputs a formatted string representation. It has no side effects, does not execute code, does not modify any data, and does not access external resources. It is deterministic formatting logic similar to other utility functions like 'add' or 'absolute_value' on the same server.
From the tool's definition Tool name 'bytes_to_human' and description 'Convert bytes to human-readable format' indicate a data conversion/formatting operation. No modifications, deletions, or external operations are performed.
Attacks that exploit this kind of access
The rule that runs bytes_to_human safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bytes_to_human, this is the rule to start with:
bytes_to_human 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 TinyFn, apply this rule, and every bytes_to_human call is checked against it from then on.
Questions about bytes_to_human
Convert bytes to human-readable format. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
bytes_to_human accepts 1 parameter: bytes_val. Required: bytes_val. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for bytes_to_human: 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 TinyFn. Nothing to install.
bytes_to_human 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 bytes_to_human 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 bytes_to_human. 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.
bytes_to_human is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue