Scan a cosmetic product INCI ingredient list for regulatory compliance and safety flags across multiple jurisdictions. Input: comma-separated INCI declaration as printed on a cosmetic product label (up to 50 ingredients). Returns per-ingredient: matched INCI name, CAS number, safety rating, EU an...
Part of the Cosmetic Regulatory server.
Free to start. No card required.
AI agents call check_formula to retrieve information from Cosmetic Regulatory 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_formula 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_formula": {}
}
}See the full Cosmetic Regulatory policy for all 4 tools.
These attack patterns abuse exactly the kind of access check_formula 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.
Scan a cosmetic product INCI ingredient list for regulatory compliance and safety flags across multiple jurisdictions. Input: comma-separated INCI declaration as printed on a cosmetic product label (up to 50 ingredients). Returns per-ingredient: matched INCI name, CAS number, safety rating, EU and US regulatory status, concern level, regulatory flags, NOAEL values, and jurisdiction-specific restrictions including max concentration limits, product-type restrictions, and regulation references. Returns overall: LOW/MODERATE/HIGH formula risk assessment, flagged ingredient count with reasons, and jurisdiction-level compliance summary. Sources: EU Regulation 1223/2009, US FDA, Korea MFDS, Japan MHLW, ASEAN, Saudi SFDA, Canada Hotlist, Australia SUSMP, China IECIC. Database: 30,553 cosmetic ingredients across 55+ jurisdictions. Use for cosmetic formula safety screening and CPSR-style triage. Do not use for single ingredient lookup (use check_ingredient) or custom MoS calculations (use calculate_mos).. It is categorised as a Read tool in the Cosmetic Regulatory MCP Server, which means it retrieves data without modifying state.
Register the Cosmetic Regulatory MCP server in PolicyLayer and add a rule for check_formula: 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 Cosmetic Regulatory. Nothing to install.
check_formula 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_formula 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_formula. 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_formula is provided by the Cosmetic Regulatory MCP server (https://roots-mcp-server.rootsbybenda.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Cosmetic Regulatory 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.