text_truncate_ellipsis
Text Truncate with Ellipsis — Shorten text to at most max_length characters, replacing the cut tail with an ellipsis marker (optionally at a word boundary).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/text-truncate-ellipsis.md
What text_truncate_ellipsis does on Gateway
AI agents call text_truncate_ellipsis to permanently remove resources in Gateway, 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 | Text to truncate |
ellipsis | string | — | Ellipsis marker (default the single-char U+2026 '…') |
max_length | integer | Yes | Maximum output length in characters |
word_boundary | boolean | — | Cut at the last whitespace before the limit instead of mid-word (default false) |
Parameters from the server's own tool schema.
Why text_truncate_ellipsis is rated Critical
An AI agent that decides to call text_truncate_ellipsis doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Gateway is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs text_truncate_ellipsis 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_truncate_ellipsis, this is the rule to start with:
text_truncate_ellipsis 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 Gateway, apply this rule, and every text_truncate_ellipsis call is checked against it from then on.
Questions about text_truncate_ellipsis
Text Truncate with Ellipsis — Shorten text to at most max_length characters, replacing the cut tail with an ellipsis marker (optionally at a word boundary). It is categorised as a Destructive tool in the Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
text_truncate_ellipsis accepts 4 parameters: text, ellipsis, max_length, word_boundary. Required: text, max_length. 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_truncate_ellipsis: 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_truncate_ellipsis 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 text_truncate_ellipsis 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_truncate_ellipsis. 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_truncate_ellipsis 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.
Across the catalogue