AI agents use text_summarize 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) |
text | string | Yes | Text to summarize (max 5000 chars) |
length | string | — | Summary length (default: medium) |
Parameters from the server's own tool schema.
An AI agent can call text_summarize faster than any human can review — one bad instruction and it creates or modifies resources in Tools by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Summarize text into concise version. Lengths: short (1-2 sentences), medium (3-5 sentences), long (full paragraph). Preserves key data and facts. 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_summarize accepts 3 parameters: lang, text, length. 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_summarize: 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_summarize 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_summarize 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_summarize. 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_summarize 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 →