truncate
Truncate to integer (remove decimal part).
This record as markdown: /tools/io-tinyfn-tinyfn/truncate.md
What truncate does on TinyFn
AI agents call truncate 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 |
|---|---|---|---|
number | number | Yes | Number to truncate |
Parameters from the server's own tool schema.
Why truncate is rated Low
This is a pure mathematical transformation that removes the decimal part of a number and returns an integer. It has no side effects, does not modify any data, and is entirely deterministic. It falls squarely in the Read/compute category.
From the tool's definition Truncate to integer (remove decimal part)
Attacks that exploit this kind of access
The rule that runs truncate 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 truncate, this is the rule to start with:
truncate 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 truncate call is checked against it from then on.
Questions about truncate
Truncate to integer (remove decimal part). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
truncate accepts 1 parameter: number. Required: number. 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 truncate: 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.
truncate 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 truncate 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 truncate. 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.
truncate 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