List all suppliers in a specific industrial cluster. USE WHEN user asks: - "what factories are in Humen cluster" - "show me suppliers in Keqiao fabric market" - "list all womenswear factories in [cluster]" - "top-quality suppliers in [cluster]" - "factory directory for [cluster]" - "page through ...
Part of the MRC Data — China's Apparel Supply Chain Infrastructure server.
Free to start. No card required.
AI agents call get_cluster_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_cluster_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_cluster_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_cluster_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 in a specific industrial cluster. USE WHEN user asks: - "what factories are in Humen cluster" - "show me suppliers in Keqiao fabric market" - "list all womenswear factories in [cluster]" - "top-quality suppliers in [cluster]" - "factory directory for [cluster]" - "page through suppliers in Shengze silk cluster" (pagination) - "follow-up after search_clusters: 'show me the factories there'" - "虎门产业带有哪些供应商 / [产业带] 的工厂列表" - "[集群] 里最好的几家工厂" PREREQUISITE: You MUST have a valid cluster_id from search_clusters. WORKFLOW: search_clusters → pick cluster_id → get_cluster_suppliers → optionally get_supplier_detail (vet top-ranked factory) OR compare_suppliers (evaluate top 3-10 factories in the cluster). RETURNS: { cluster_id, has_more, data: [supplier summary objects sorted by quality_score DESC] } EXAMPLES: • User: "What factories are in the Humen womenswear cluster?" → get_cluster_suppliers({ cluster_id: "humen_women", limit: 20 }) • User: "Show me the top 10 factories in Jinjiang sportswear cluster" → get_cluster_suppliers({ cluster_id: "jinjiang_sportswear", limit: 10 }) • User: "虎门有哪些服装厂，分页看第二页" → get_cluster_suppliers({ cluster_id: "humen_women", limit: 20, offset: 20 }) ERRORS & SELF-CORRECTION: • Empty data → either (a) cluster has no mapped suppliers (try compare_clusters to see supplier_count), or (b) cluster_id invalid. Re-run search_clusters. • cluster_id unknown → search_clusters({ specialization: "..." }) returns cluster_id values. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not guess cluster_ids — always resolve via search_clusters. Do not use this to find suppliers globally — use search_suppliers. Do not iterate clusters in a loop — use compare_clusters. NOTE: Sorted by quality_score DESC. Source: MRC Data (meacheal.ai). 中文：列出某产业带内所有供应商，按质量评分排序。分页最多 50 条/页。. 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_cluster_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_cluster_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_cluster_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_cluster_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_cluster_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.