Remove all whitespace from text.
AI agents call remove_whitespace 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 process |
Parameters from the server's own tool schema.
An AI agent that decides to call remove_whitespace 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
Remove all whitespace from text. 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.
remove_whitespace accepts 1 parameter: text. 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 remove_whitespace: 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.
remove_whitespace 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 remove_whitespace 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 remove_whitespace. 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.
remove_whitespace 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.
remove_whitespace is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →