List all suppliers offering a specific fabric, sorted by quality score, with price comparison. USE WHEN user asks: - "who supplies fabric fab_XXX" / "where can I buy this fabric" - "compare prices for [fabric] across suppliers" - "best supplier for [fabric specification]" - "which factory has the...
Part of the MRC Data — China's Apparel Supply Chain Infrastructure server.
Free to start. No card required.
AI agents call get_fabric_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 get_fabric_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.
{
"version": "1",
"default": "deny",
"tools": {
"get_fabric_suppliers": {}
}
}See the full MRC Data — China's Apparel Supply Chain Infrastructure policy for all 19 tools.
These attack patterns abuse exactly the kind of access get_fabric_suppliers gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List all suppliers offering a specific fabric, sorted by quality score, with price comparison. USE WHEN user asks: - "who supplies fabric fab_XXX" / "where can I buy this fabric" - "compare prices for [fabric] across suppliers" - "best supplier for [fabric specification]" - "which factory has the lowest price on FAB-XXX" - "rank suppliers by quality for this fabric" - "follow-up: 'who else sells this?'" - "source comparison for [fabric]" - "price spread on FAB-XXX" - "谁家有这块面料 / 哪个厂报价最低 / 面料供应商对比" - "[面料] 有哪些供应商 / 货源" Returns supplier records linked to the fabric with: company name, location, quality score, and that supplier's quoted price + MOQ for the fabric. Sorted by supplier quality score so the most reliable options appear first. PREREQUISITE: You MUST have a valid fabric_id from search_fabrics. WORKFLOW: search_fabrics → pick fabric_id → get_fabric_suppliers → optionally get_supplier_detail (vet the top-ranked supplier) OR compare_suppliers (up to 10 IDs from this list). RETURNS: { fabric_id, count, data: [{ supplier_id, company_name_cn, province, city, quality_score, price_rmb, moq }] } EXAMPLES: • User: "Who supplies FAB-W007 and at what price?" → get_fabric_suppliers({ fabric_id: "FAB-W007" }) • User: "Compare all suppliers for fabric FAB-K023" → get_fabric_suppliers({ fabric_id: "FAB-K023" }) • User: "FAB-123 有哪些供应商" → get_fabric_suppliers({ fabric_id: "FAB-123" }) ERRORS & SELF-CORRECTION: • count=0 → no suppliers linked to this fabric. Either (a) fabric is a spec-sheet reference with no mapped source, or (b) suppliers carry this fabric but the link isn't captured. Try search_suppliers filtered by the fabric's typical specialization (e.g. denim cluster) instead. • "Fabric not found" (implicit) → fabric_id invalid. Re-run search_fabrics. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call this to browse suppliers generally — use search_suppliers. Do not call to see a supplier's full fabric range — use get_supplier_fabrics. NOTE: Source: MRC Data (meacheal.ai). Sorted by supplier quality_score DESC. 中文：查询某面料的所有供应商，按质量评分排序，含报价对比。. 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.
Register the MRC Data — China's Apparel Supply Chain Infrastructure MCP server in PolicyLayer and add a rule for get_fabric_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.
get_fabric_suppliers 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 get_fabric_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.
Set action: deny in the PolicyLayer policy for get_fabric_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.
get_fabric_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.
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.