AI agents use rednote_rewrite_in_style to create or update resources in Rednote Analyzer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rednote Analyzer environment.
The tool name suggests rewriting content in a particular style, which is a Write operation (generating/modifying text content). The server description mentions generating content for RedNote. However, the description is empty, so confidence is lowered. Based on sibling tools like 'rednote_generate_post', this likely produces/modifies text content rather than posting it, keeping it in the Write category.
From the tool's definition Tool name 'rednote_rewrite_in_style' and server context of content generation for Xiaohongshu (RedNote).
Documented attack patterns abuse exactly the kind of access rednote_rewrite_in_style gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rednote Analyzer, and nothing reaches the server without passing your rules. This is the rule we recommend for rednote_rewrite_in_style:
{
"version": "1",
"default": "deny",
"tools": {
"rednote_rewrite_in_style": {
"limits": [
{
"counter": "rednote_rewrite_in_style_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} rednote_rewrite_in_style stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
rednote_rewrite_in_style. It is categorised as a Write tool in the Rednote Analyzer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rednote Analyzer MCP server in PolicyLayer and add a rule for rednote_rewrite_in_style: 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 Rednote Analyzer. Nothing to install.
rednote_rewrite_in_style 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 rednote_rewrite_in_style 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 rednote_rewrite_in_style. 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.
rednote_rewrite_in_style is provided by the Rednote Analyzer MCP server (shellydeng08/rednote-analyzer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rednote Analyzer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Rednote Analyzer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.