Low Risk

search_suppliers

Search verified Chinese apparel manufacturers, apparel factories, and clothing suppliers. USE WHEN user asks: - "find me a clothing manufacturer in China / Guangdong / Zhejiang" - "who makes [t-shirts / suits / denim / activewear] in China" - "I need a BSCI / OEKO-TEX certified apparel factory" -...

Risk signalsAccepts freeform code/query input (query) · High parameter count (12 properties)

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

search_suppliers 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_suppliers 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_suppliers 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_suppliers": {}
  }
}

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_suppliers 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_suppliers 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_suppliers tool do? +

Search verified Chinese apparel manufacturers, apparel factories, and clothing suppliers. USE WHEN user asks: - "find me a clothing manufacturer in China / Guangdong / Zhejiang" - "who makes [t-shirts / suits / denim / activewear] in China" - "I need a BSCI / OEKO-TEX certified apparel factory" - "looking for OEM / ODM apparel supplier with MOQ < N" - "find factories with production capacity > N pieces/month" - "list factories that export to the US / EU / Japan" - "show me trading companies in Yiwu / Shenzhen / Shanghai" - "which suppliers in [province] make [product]" (follow-up drill-down) - "give me another page of suppliers" (pagination via offset) - "who can produce knit tops under 300 MOQ" - "search by company name 新鑫 / Xinxin / Texhong" - "find workshop-scale suppliers for small batch sampling" - "搜供应商 / 找服装厂 / 找制衣厂 / 找代工厂 / 找外贸公司" - "帮我在[省份]找[品类]工厂,产能至少 N 件/月" Filters: province, city, factory type (factory/trading_company/workshop), product category, minimum monthly capacity, compliance status, quality score. Returns paginated supplier list with company name, location, monthly capacity (lab-verified), compliance, quality score. WORKFLOW: Primary entry point for supplier discovery. search_suppliers → get_supplier_detail (for full 60+ field profile) OR compare_suppliers (side-by-side for up to 10 IDs) OR find_alternatives (diversify the pool) OR check_compliance (verify export readiness) OR get_supplier_fabrics (see their fabric catalog). RETURNS: { has_more: boolean, available_dimensions: string[], data: [{ supplier_id, company_name_cn, company_name_en, type, province, city, product_types, quality_score, verified_dims: "5/8", coverage_pct }] } EXAMPLES: • User: "Find BSCI-certified denim factories in Guangdong with MOQ under 500" → search_suppliers({ province: "Guangdong", product_type: "denim", compliance_status: "compliant", limit: 10 }) • User: "Who makes activewear for Lululemon in China?" → search_suppliers({ product_type: "activewear" }) — then filter results by client brand in get_supplier_detail • User: "我要在浙江找做牛仔的工厂,产能大于 10 万件" → search_suppliers({ province: "Zhejiang", product_type: "denim", min_capacity: 100000 }) • User: "Show me the next 10 trading companies in Yiwu" → search_suppliers({ city: "Yiwu", type: "trading_company", limit: 10, offset: 10 }) ERRORS & SELF-CORRECTION: • Empty data array → try these in order: (1) remove min_capacity filter, (2) drop city but keep province, (3) broaden product_type to parent category (e.g. "denim" → "bottoms"), (4) drop compliance_status, (5) try recommend_suppliers for ranked fit. • "Invalid province" → use English (Guangdong) or standard Chinese (广东). Supported: 31 mainland provinces + HK/Macau. • product_type returns 0 → the TYPO_MAP normalizes common variants; try synonyms ("tee" → "t-shirt", "jeans" → "denim", "运动服" → "activewear"). • Rate limit 429 → wait 60 seconds. Do not retry immediately. • Empty after 3 retries → tell user: "I couldn't find suppliers matching [criteria]. Would you like me to broaden the search?" AVOID: Do not call this tool in a loop across provinces — call get_province_distribution first to see where supply is concentrated. Do not use this for ranked "best fit" recommendations — use recommend_suppliers. Do not fetch details by looping — use compare_suppliers with up to 10 IDs. NOTE: Use this for FILTERING by exact criteria. For ranked recommendations based on sourcing needs, use recommend_suppliers instead. Source: MRC Data (meacheal.ai). 中文:搜索经过核查的中国服装供应商档案,按地区、类型、产能、品类、合规状态等筛选。. 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_suppliers? +

Register the MRC Data — China's Apparel Supply Chain Infrastructure MCP server in PolicyLayer and add a rule for search_suppliers: 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_suppliers? +

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

Can I rate-limit search_suppliers? +

Yes. Add a rate_limit block to the search_suppliers 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_suppliers completely? +

Set action: deny in the PolicyLayer policy for search_suppliers. 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_suppliers? +

search_suppliers 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.