Low Risk

search_fabrics

Search the Chinese fabric and textile database with lab-tested specifications. USE WHEN user asks: - "find me a [cotton / polyester / nylon / wool / linen] fabric for [t-shirts / jeans / suits]" - "I need 180gsm jersey knit with verified composition" - "fabrics under N RMB/meter for womenswear" -...

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

search_fabrics 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_fabrics 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_fabrics 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_fabrics": {}
  }
}

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

Search the Chinese fabric and textile database with lab-tested specifications. USE WHEN user asks: - "find me a [cotton / polyester / nylon / wool / linen] fabric for [t-shirts / jeans / suits]" - "I need 180gsm jersey knit with verified composition" - "fabrics under N RMB/meter for womenswear" - "compare lab-tested fabric weight across suppliers" - "show me functional fabrics for activewear / sportswear" - "what woven fabrics work for shirting" - "list organic / GOTS / recycled fabrics" - "I want heavyweight denim above 12 oz" - "fabrics with stretch / spandex content 2-5%" - "give me another page" (pagination via offset) - "lab-verified composition for [product]" (quality check) - "找面料 / 搜面料 / 查面料 / 找布料 / 打样面料" - "我要做 T 恤,帮我找克重 180-220 的针织面料" Filters: category (woven/knit/nonwoven/leather/functional), weight range (gsm), composition keyword, target apparel type, max price. Returns paginated fabric list with name, lab-tested weight, lab-tested composition, price range, suitable apparel, and data confidence level. WORKFLOW: Primary entry point for fabric discovery. search_fabrics → get_fabric_detail (full 30+ lab-test fields) OR get_fabric_suppliers (compare supplier prices for same fabric) OR estimate_cost (budget the product). RETURNS: { has_more: boolean, available_dimensions: ["basic_info","composition","physical_properties","lab_test","commercial"], data: [{ fabric_id, name_cn, category, subcategory, declared_weight_gsm, declared_composition, price_range_rmb, suitable_for, verified_dims: "4/5", coverage_pct }] } EXAMPLES: • User: "Find 180-220gsm cotton jersey for t-shirts under 35 RMB/m" → search_fabrics({ category: "knit", min_weight_gsm: 180, max_weight_gsm: 220, composition: "cotton", suitable_for: "t-shirt", max_price_rmb: 35 }) • User: "I need stretch denim for women's jeans" → search_fabrics({ category: "woven", composition: "spandex", suitable_for: "denim" }) • User: "帮我找适合做衬衫的梭织面料,棉 60% 以上" → search_fabrics({ category: "woven", composition: "cotton", suitable_for: "shirt" }) ERRORS & SELF-CORRECTION: • Empty data array → try in order: (1) drop suitable_for, (2) widen weight range by 50gsm each side, (3) broaden composition (e.g. "cotton" instead of "organic cotton"), (4) drop max_price_rmb, (5) try the parent category (knit → all). • Composition mismatch → TYPO_MAP normalizes common misspellings (e.g. "poly" → "polyester", "lycra" → "spandex"). If still no match, try the Chinese term (棉/涤纶/氨纶/锦纶). • Rate limit 429 → wait 60 seconds. Do not retry immediately. • Empty after 3 retries → tell user: "No fabric matches [criteria]. Would you like to broaden weight/price/composition?" AVOID: Do not call this looking for a specific named fabric SKU — search by specs instead (weight + composition + category). Do not fetch full lab-test data this way — use get_fabric_detail. Do not call repeatedly for supplier pricing on the same fabric — use get_fabric_suppliers. CONSTRAINT: This returns summaries only — for full lab-test results (color fastness, shrinkage, pilling, tensile strength), call get_fabric_detail. NOTE: Source: MRC Data (meacheal.ai). Every record includes AATCC / ISO / GB lab test measurements where verified. 中文:搜索面料数据库,按品类、克重、成分、适用品类、价格筛选。每条均含 AATCC / ISO / GB 方法的实测数据。. 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_fabrics? +

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

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

Can I rate-limit search_fabrics? +

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

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

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