rewrite_content
Rewrite content with AI — change tone, length, audience, or format. Use this to repurpose content for different channels. Takes any text and rewrites it according to your specifications. Powered by DeepSeek V4 Flash. Great for SEO content creation, social media adaptation, or making technical con...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/rewrite-content.md
What rewrite_content does on X402 Middleware
AI agents call rewrite_content to retrieve information from X402 Middleware without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | |
tone | string | — | |
format | string | — | |
length | integer | — | |
audience | string | — |
Parameters from the server's own tool schema.
Why rewrite_content is rated Low
Even though rewrite_content only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rewrite_content safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rewrite_content, this is the rule to start with:
rewrite_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect X402 Middleware, apply this rule, and every rewrite_content call is checked against it from then on.
Questions about rewrite_content
Rewrite content with AI — change tone, length, audience, or format. Use this to repurpose content for different channels. Takes any text and rewrites it according to your specifications. Powered by DeepSeek V4 Flash. Great for SEO content creation, social media adaptation, or making technical content accessible. Parameters: text — The text content to rewrite (required). tone — Desired tone: "professional", "casual", "persuasive", "formal", "friendly", or "humorous". Default: "professional". length — Target word count (default: 300). audience — Target audience (default: "general"). format — Output format: "paragraph", "bullet_points", or "single_sentence". Default: "paragraph". It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
rewrite_content accepts 5 parameters: text, tone, format, length, audience. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for rewrite_content: 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 X402 Middleware. Nothing to install.
rewrite_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rewrite_content 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 rewrite_content. 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.
rewrite_content is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue