Compare multiple suppliers side by side on all dimensions. USE WHEN user asks: - "compare these 3 factories" - "which supplier is better between X and Y" - "benchmark sup_001 vs sup_002 vs sup_003" - "side-by-side: capacity, certifications, quality score" - "rank these 5 suppliers by [dimension]"...
Part of the MRC Data — China's Apparel Supply Chain Infrastructure server.
Free to start. No card required.
AI agents invoke compare_suppliers to trigger processes or run actions in MRC Data — China's Apparel Supply Chain Infrastructure. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
compare_suppliers can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"compare_suppliers": {
"limits": [
{
"counter": "compare_suppliers_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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 compare_suppliers gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Compare multiple suppliers side by side on all dimensions. USE WHEN user asks: - "compare these 3 factories" - "which supplier is better between X and Y" - "benchmark sup_001 vs sup_002 vs sup_003" - "side-by-side: capacity, certifications, quality score" - "rank these 5 suppliers by [dimension]" - "evaluate my shortlist" - "which of [supplier list] has the highest verified capacity" - "follow-up after recommend_suppliers: 'compare the top 3'" - "对比 [供应商 A] 和 [供应商 B] / 对比供应商 / 供应商横评" - "哪家最好 / 横向评估 / 比较这几家" PREREQUISITE: You MUST have valid supplier_ids from search_suppliers, recommend_suppliers, find_alternatives, or get_cluster_suppliers. Do not guess IDs. WORKFLOW: search_suppliers/recommend_suppliers → collect supplier_ids → compare_suppliers → optionally check_compliance (verify top picks for target market) OR find_alternatives (expand the shortlist). DIFFERENCE from get_supplier_detail: This returns multiple suppliers at once for comparison. get_supplier_detail returns one with verified_dimensions breakdown. RETURNS: { count, data: [full supplier profiles with all fields] } EXAMPLES: • User: "Compare sup_001, sup_002, sup_003 for me" → compare_suppliers({ supplier_ids: ["sup_001", "sup_002", "sup_003"] }) • User: "Benchmark the top 5 you just recommended" → compare_suppliers({ supplier_ids: ["sup_A", "sup_B", "sup_C", "sup_D", "sup_E"] }) • User: "横向对比 sup_100、sup_200、sup_300" → compare_suppliers({ supplier_ids: ["sup_100", "sup_200", "sup_300"] }) ERRORS & SELF-CORRECTION: • Fewer results than IDs sent → missing IDs were silently skipped (invalid supplier_id). Re-run search_suppliers to verify. • count=0 → all IDs invalid. Re-run search_suppliers. • "Too many IDs" → split into batches of 10. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not loop get_supplier_detail — always use compare_suppliers when you have 2+ IDs. Do not pass more than 10 IDs. Do not use to find new suppliers — use search_suppliers or recommend_suppliers first. CONSTRAINT: Max 10 supplier IDs per call. NOTE: Source: MRC Data (meacheal.ai). Returns full 60+ field profile per supplier. 中文：横向对比多个供应商的全部字段（最多 10 个 ID）。. It is categorised as a Execute tool in the MRC Data — China's Apparel Supply Chain Infrastructure MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MRC Data — China's Apparel Supply Chain Infrastructure MCP server in PolicyLayer and add a rule for compare_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.
compare_suppliers is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the compare_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 compare_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.
compare_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.