Check if a supplier meets compliance requirements for a target export market. USE WHEN: - User asks "can this factory export to the US/EU/Japan" - User needs to verify certifications for a specific market - "UFLPA / Xinjiang cotton / REACH / JIS / KC check on sup_XXX" - "is [supplier] ready for E...
Part of the MRC Data — China's Apparel Supply Chain Infrastructure server.
Free to start. No card required.
AI agents call check_compliance 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 check_compliance 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": {
"check_compliance": {}
}
}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 check_compliance 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.
Check if a supplier meets compliance requirements for a target export market. USE WHEN: - User asks "can this factory export to the US/EU/Japan" - User needs to verify certifications for a specific market - "UFLPA / Xinjiang cotton / REACH / JIS / KC check on sup_XXX" - "is [supplier] ready for EU CSDDD / Forced Labor Regulation" - "what's missing for sup_XXX to export to US" - "gap analysis / compliance dossier for [supplier] → [market]" - "does [supplier] meet Japan formaldehyde / azo dye rules" - "follow-up after get_supplier_detail: 'is this one US-ready?'" - "能不能出口美国 / 欧盟 / 日本 / 韩国" - "合规检查 / 认证要求 / 出口资质 / 强制性法规 / UFLPA 合规" - "[供应商] 能否满足 [市场] 的准入要求" PREREQUISITE: You MUST have a valid supplier_id from search_suppliers, get_supplier_detail, or recommend_suppliers. WORKFLOW: search_suppliers → check_compliance → if issues exist, use find_alternatives to source compliant alternatives OR get_supplier_detail to see the full compliance fields and coverage. RETURNS: { supplier_id, company_name, target_market, overall_ready: boolean, passed: [string], issues: [string], certifications: [string], market_requirements: {field: value}, note } EXAMPLES: • User: "Can sup_001 export to the US? Check UFLPA compliance" → check_compliance({ supplier_id: "sup_001", target_market: "us" }) • User: "Is Texhong EU REACH compliant?" → check_compliance({ supplier_id: "sup_texhong_042", target_market: "eu" }) • User: "sup_234 能出口日本吗" → check_compliance({ supplier_id: "sup_234", target_market: "japan" }) ERRORS & SELF-CORRECTION: • "Supplier not found" → supplier_id invalid. Re-run search_suppliers. • passed=[] AND issues=["No specific issues found, but data may be incomplete"] → the supplier's compliance fields are mostly null. Interpret as UNKNOWN not COMPLIANT. Tell user: "Compliance data incomplete — recommend verifying directly with the supplier." • overall_ready=false with many issues → use find_alternatives to find backup suppliers, OR search_suppliers with compliance_status="compliant" to filter upfront. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call this in a loop across all suppliers — instead pre-filter via search_suppliers({ compliance_status: "compliant" }). Do not treat missing fields as non-compliant — report them as "not confirmed". Do not use for general supplier info — use get_supplier_detail. NOTE: Many suppliers have incomplete compliance data. Missing data = "not confirmed", not "non-compliant". Source: MRC Data (meacheal.ai). Market requirements cover UFLPA/Xinjiang (US), REACH/CSDDD/Forced Labor Reg (EU), formaldehyde/azo/JIS (Japan), KC (Korea). 中文：检查某供应商是否满足目标出口市场（美/欧/日/韩）的合规要求。. 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 check_compliance: 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.
check_compliance 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 check_compliance 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 check_compliance. 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.
check_compliance 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.