AI agents use text_rewrite to create or update resources in Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tools environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | Language (default: zh) |
mode | string | — | Rewriting mode (default: standard) |
text | string | Yes | Text to rewrite (max 3000 chars) |
Parameters from the server's own tool schema.
This tool creates or modifies text reversibly by applying stylistic transformations while preserving meaning. It does not execute code, delete data, move money, or trigger external operations. The output is a new version of input text that can be easily undone or regenerated, making it a Write operation with low severity since misuse would only affect text styling, not critical systems or data integrity.
From the tool's definition Tool description states it 'Rewrite[s] text with different styles' with modes including standard, creative, academic, and casual—all modes modify/transform text content without deletion or irreversibility.
Attacks that exploit this kind of access
Rewrite text with different styles while preserving meaning. Modes: standard (natural), creative (expressive), academic (formal), casual (informal). It is categorised as a Write tool in the Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
text_rewrite accepts 3 parameters: lang, mode, text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for text_rewrite: 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 Tools. Nothing to install.
text_rewrite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the text_rewrite 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_rewrite. 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_rewrite is provided by the Tools MCP server (https://www.jiebang.site/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →