AI agents use ai_text_generate 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 |
|---|---|---|---|
type | string | — | Generation type (default: copywriting) |
input | string | Yes | Input text or topic (max 500 chars) |
style | string | — | Additional style requirement (optional) |
Parameters from the server's own tool schema.
An AI agent can call ai_text_generate 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
AI-powered text generation: copywriting, naming, slogans, catchy titles, praise/replies, couplets. Powered by GLM-4.7-Flash (free, 10k calls/day). 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.
ai_text_generate accepts 3 parameters: type, input, style. Required: input. 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 ai_text_generate: 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.
ai_text_generate 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 ai_text_generate 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 ai_text_generate. 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.
ai_text_generate 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 →