This record as markdown: /tools/io-tinyfn-tinyfn/format-bytes.md
What format_bytes does on TinyFn
AI agents call format_bytes 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 |
|---|---|---|---|
binary | boolean | — | Use binary (1024) or decimal (1000) units |
bytes_value | integer | Yes | Size in bytes |
Parameters from the server's own tool schema.
Why format_bytes is rated Low
This is a deterministic utility function that converts numeric byte values into human-readable format (e.g., 1024 → '1 KB'). It retrieves/transforms data without modifying any state, executing code, or triggering external operations. It is a Read category tool with low severity due to minimal risk if misused by an AI agent.
From the tool's definition Tool name 'format_bytes' and description 'Format bytes to human-readable size' indicate a pure data transformation function that reads input and returns formatted output with no side effects, state changes, or external operations.
Attacks that exploit this kind of access
The rule that runs format_bytes 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 format_bytes, this is the rule to start with:
format_bytes 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 format_bytes call is checked against it from then on.
Questions about format_bytes
Format bytes to human-readable size. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
format_bytes accepts 2 parameters: binary, bytes_value. Required: bytes_value. 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 format_bytes: 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.
format_bytes 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 format_bytes 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 format_bytes. 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.
format_bytes 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