text_wordwrap
Text Word-Wrap / Reflow — Wrap plain text to a fixed column width (stdlib textwrap), returning either an array of lines or a single re-flowed string.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/text-wordwrap.md
What text_wordwrap does on Gateway
AI agents call text_wordwrap to retrieve information from Gateway 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 |
|---|---|---|---|
mode | string | — | wrap | fill (default wrap) |
text | string | Yes | Text to wrap |
width | integer | — | Max characters per line, 1-1000 (default 70) |
break_long_words | boolean | — | Split a word longer than width across lines (default true) |
Parameters from the server's own tool schema.
Why text_wordwrap is rated Low
The tool only reformats and returns text output without modifying underlying data, executing code, deleting information, or triggering financial transactions. It is a pure text processing function analogous to a 'get' or 'format' operation, making it a Read category risk with minimal blast radius.
From the tool's definition Tool name is 'text_wordwrap' and description states it performs 'Text Word-Wrap / Reflow — Wrap plain text to a fixed column width (stdlib textwrap), returning either an array of lines or a single re-flowed string.' This is a text formatting/transformation…
Attacks that exploit this kind of access
The rule that runs text_wordwrap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For text_wordwrap, this is the rule to start with:
text_wordwrap 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 Gateway, apply this rule, and every text_wordwrap call is checked against it from then on.
Questions about text_wordwrap
Text Word-Wrap / Reflow — Wrap plain text to a fixed column width (stdlib textwrap), returning either an array of lines or a single re-flowed string. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
text_wordwrap accepts 4 parameters: mode, text, width, break_long_words. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for text_wordwrap: 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 Gateway. Nothing to install.
text_wordwrap 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_wordwrap 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_wordwrap. 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_wordwrap is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue