AI agents use meta_desc_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 |
|---|---|---|---|
lang | string | — | Language (default: zh) |
title | string | Yes | Page title (required) |
content | string | — | Content summary (optional) |
keyword | string | — | Target keyword (optional) |
Parameters from the server's own tool schema.
This tool creates a new SEO meta description string based on provided inputs, which is a reversible Write operation. It does not execute code, delete data, access sensitive systems, or move money. The generated output can be discarded or replaced without consequence, making it low severity even though it is a Write operation.
From the tool's definition Tool generates and produces SEO meta description content from inputs (title, keyword, content). The verb 'Generate' combined with output creation indicates a Write operation—it creates new data artifact (meta description string).
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
Generate SEO-friendly meta description (120-160 chars) from title, keyword, and content. Includes call-to-action and keyword placement. 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.
meta_desc_generate accepts 4 parameters: lang, title, content, keyword. Required: title. 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 meta_desc_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.
meta_desc_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 meta_desc_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 meta_desc_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.
meta_desc_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 →