AI agents call text_clean to retrieve information from Onion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool processes text in-memory by removing formatting artifacts. It does not persist data, execute code, modify external systems, or cause destructive side effects. It is a pure text transformation utility with no external impact.
From the tool's definition 清理文本：去除多余空行、首尾空白、重复行等 (Clean text: remove extra blank lines, leading/trailing whitespace, duplicate lines, etc.)
Attacks that exploit this kind of access
清理文本：去除多余空行、首尾空白、重复行等。. It is categorised as a Read tool in the Onion MCP Server, which means it retrieves data without modifying state.
Register the Onion MCP server in PolicyLayer and add a rule for text_clean: 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 Onion. Nothing to install.
text_clean 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 text_clean 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_clean. 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_clean is provided by the Onion MCP server (onion-ai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
text_clean is one line of Onion's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →