This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/text-wrap.md
What text_wrap does on UnClick
AI agents call text_wrap to retrieve information from UnClick 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 |
|---|---|---|---|
text | string | Yes | Text to wrap. |
width | number | — | Column width (10-200, default 80). |
Parameters from the server's own tool schema.
Why text_wrap is rated Low
This tool performs text formatting only. It takes text as input, applies wrapping logic based on column width parameters, and returns the formatted result. There is no data creation, modification, deletion, code execution, or financial impact. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool description states it "Hard-wrap text to a specified column width" — a pure text formatting operation that reads input and returns reformatted output with no side effects, data modification, or external operations.
Attacks that exploit this kind of access
The rule that runs text_wrap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_wrap, this is the rule to start with:
text_wrap 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 UnClick, apply this rule, and every text_wrap call is checked against it from then on.
Questions about text_wrap
Hard-wrap text to a specified column width. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
text_wrap accepts 2 parameters: text, width. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for text_wrap: 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 UnClick. Nothing to install.
text_wrap 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 text_wrap 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 text_wrap. 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.
text_wrap is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue