This record as markdown: /tools/io-tinyfn-tinyfn/truncate-2.md
What truncate_2 does on TinyFn
AI agents call truncate_2 to permanently remove resources in TinyFn, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | The text to truncate |
length | integer | — | Maximum length |
suffix | string | — | Suffix to add if truncated |
Parameters from the server's own tool schema.
Why truncate_2 is rated Critical
An AI agent that decides to call truncate_2 doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from TinyFn is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs truncate_2 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_2, this is the rule to start with:
truncate_2 is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every truncate_2 call is checked against it from then on.
Questions about truncate_2
Truncate text to a specified length. It is categorised as a Destructive tool in the TinyFn MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
truncate_2 accepts 3 parameters: text, length, suffix. Required: text. 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_2: 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_2 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the truncate_2 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_2. 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_2 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.
Across the catalogue