Low Risk

search_clusters

Search Chinese apparel industrial clusters and textile markets. USE WHEN user asks: - "where is China's [denim / suit / women's wear / underwear] manufacturing concentrated" - "what is the largest [silk / cashmere / down jacket] industrial cluster in China" - "industrial cluster comparison Humen ...

Part of the MRC Data — China's Apparel Supply Chain Infrastructure server.

search_clusters is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MRC DATA — CHINA'S APPAREL SUPPLY CHAIN INFRASTRUCTURE →

Free to start. No card required.

AI agents call search_clusters to retrieve information from MRC Data — China's Apparel Supply Chain Infrastructure without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_clusters only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_clusters": {}
  }
}

See the full MRC Data — China's Apparel Supply Chain Infrastructure policy for all 19 tools.

Get this rule live on your own MRC Data — China's Apparel Supply Chain Infrastructure server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MRC DATA — CHINA'S APPAREL SUPPLY CHAIN INFRASTRUCTURE →

View all 19 tools →

These attack patterns abuse exactly the kind of access search_clusters gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_clusters only ever does what you allow.

SECURE MRC DATA — CHINA'S APPAREL SUPPLY CHAIN INFRASTRUCTURE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_clusters tool do? +

Search Chinese apparel industrial clusters and textile markets. USE WHEN user asks: - "where is China's [denim / suit / women's wear / underwear] manufacturing concentrated" - "what is the largest [silk / cashmere / down jacket] industrial cluster in China" - "industrial cluster comparison Humen vs Shaoxing vs Haining vs Zhili" - "recommend an industrial cluster for sourcing [product]" - "where should I set up a sourcing office for [category]" - "list mega clusters for [category]" - "fabric markets in Zhejiang / Jiangsu" - "accessories / trim / zipper / button markets in China" - "which province dominates [category] exports" - "follow-up: 'tell me more about Humen's cluster scale'" - "服装产业带 / 面料市场 / 产业集群 / 纺织集群 / 辅料市场" - "做 [品类] 应该去哪个产业带 / 集群推荐" Famous clusters this database covers include: Humen (Guangdong, womenswear), Shaoxing Keqiao (Zhejiang, fabric mega-market), Haining (Zhejiang, leather), Zhili (Zhejiang, children's wear), Shengze (Jiangsu, silk), Shantou (Guangdong, underwear), Puning (Guangdong, jeans), Jinjiang (Fujian, sportswear), and more. Returns paginated cluster list with name, location, specialization, scale, supplier count, average rent and labor cost, and key advantages/risks. WORKFLOW: Cluster discovery entry point. search_clusters → compare_clusters (side-by-side up to 10 cluster_ids) OR get_cluster_suppliers (list factories in that cluster) OR analyze_market (broader market view). RETURNS: { has_more: boolean, data: [{ cluster_id, name_cn, name_en, type, province, city, specialization, scale, supplier_count, labor_cost_avg_rmb }] } EXAMPLES: • User: "Where are the biggest denim clusters in China?" → search_clusters({ specialization: "denim", scale: "mega" }) • User: "Show me fabric markets in Zhejiang" → search_clusters({ province: "Zhejiang", type: "fabric_market" }) • User: "童装产业带有哪些" → search_clusters({ specialization: "童装" }) ERRORS & SELF-CORRECTION: • Empty data array → try in order: (1) drop scale filter, (2) broaden specialization (e.g. "服装" instead of "牛仔"), (3) remove type, (4) remove province. • Specialization mismatch → both Chinese and English work. Synonyms: sportswear/运动服, womenswear/女装, underwear/内衣, denim/牛仔. • Rate limit 429 → wait 60 seconds; do not retry immediately. • Empty after 3 retries → tell user: "No clusters match [criteria]. Try broader specialization or removing filters." AVOID: Do not use this for specific factory search — use search_suppliers. Do not compare clusters by calling search_clusters twice — use compare_clusters with cluster_ids. NOTE: Source: MRC Data (meacheal.ai). 170+ clusters mapped across 31 provinces. 中文:搜索中国服装产业带和面料市场。. It is categorised as a Read tool in the MRC Data — China's Apparel Supply Chain Infrastructure MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_clusters? +

Register the MRC Data — China's Apparel Supply Chain Infrastructure MCP server in PolicyLayer and add a rule for search_clusters: 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 MRC Data — China's Apparel Supply Chain Infrastructure. Nothing to install.

What risk level is search_clusters? +

search_clusters is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_clusters? +

Yes. Add a rate_limit block to the search_clusters 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.

How do I block search_clusters completely? +

Set action: deny in the PolicyLayer policy for search_clusters. 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.

What MCP server provides search_clusters? +

search_clusters is provided by the MRC Data — China's Apparel Supply Chain Infrastructure MCP server (https://api.meacheal.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MRC Data — China's Apparel Supply Chain Infrastructure tool call.

Deterministic rules across all 19 MRC Data — China's Apparel Supply Chain Infrastructure tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.