AI 深度搜索引擎。搜索多个网页，抓取全文内容，返回结构化 Research Brief。 【什么时候用】 - 需要深入分析的问题（
AI agents call wuxing_search to retrieve information from Wuxing Search MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the 'Execute' framing in the description (the term '深度搜索引擎' could suggest code execution), the actual functionality described is querying multiple web pages and extracting full-text content, then returning structured results. This is inherently a Read operation: it retrieves and aggregates data with no side effects, no data modification, and no command execution capability.
From the tool's definition Tool performs web searching and content retrieval ('搜索多个网页，抓取全文内容') without modifying, deleting, or executing operations. Returns 'structured Research Brief' - a read-only data retrieval operation.
Documented attack patterns abuse exactly the kind of access wuxing_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wuxing Search MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for wuxing_search:
{
"version": "1",
"default": "deny",
"tools": {
"wuxing_search": {}
}
}wuxing_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
AI 深度搜索引擎。搜索多个网页，抓取全文内容，返回结构化 Research Brief。 【什么时候用】 - 需要深入分析的问题（. It is categorised as a Read tool in the Wuxing Search MCP MCP Server, which means it retrieves data without modifying state.
Register the Wuxing Search MCP server in PolicyLayer and add a rule for wuxing_search: 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 Wuxing Search MCP. Nothing to install.
wuxing_search 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 wuxing_search 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 wuxing_search. 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.
wuxing_search is provided by the Wuxing Search MCP server (maeshughes/wuxing-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuxing Search MCP, 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.
3 Wuxing Search MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.