Calculate Margin of Safety for a cosmetic ingredient at a specific concentration following SCCS Notes of Guidance methodology. Input: ingredient name/INCI/CAS, concentration percentage, product type (e.g. 'body lotion', 'shampoo', 'lipstick'), optional body weight and dermal absorption override. ...
Part of the Cosmetic Regulatory server.
Free to start. No card required.
AI agents call calculate_mos 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 calculate_mos 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": {
"calculate_mos": {}
}
}See the full Cosmetic Regulatory policy for all 4 tools.
These attack patterns abuse exactly the kind of access calculate_mos 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.
Calculate Margin of Safety for a cosmetic ingredient at a specific concentration following SCCS Notes of Guidance methodology. Input: ingredient name/INCI/CAS, concentration percentage, product type (e.g. 'body lotion', 'shampoo', 'lipstick'), optional body weight and dermal absorption override. Returns: NOAEL value with study source (species, route, duration), SCCS exposure parameters (daily exposure, retention factor), Systemic Exposure Dose (SED) calculation, Margin of Safety value, pass/fail assessment against MoS>100 threshold, and recommended maximum concentration if MoS fails. Sources: SCCS Notes of Guidance (11th Revision, SCCS/1628/21), NOAEL studies from ECHA/ToxValDB, SCCS exposure parameter tables. Database: 174,973 NOAEL studies searched for best available value. Use for cosmetic ingredient exposure assessment and safety calculations. Do not use for regulatory lookup alone (use check_ingredient), formula screening (use check_formula), or food/pharmaceutical exposure calculations.. 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 calculate_mos: 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.
calculate_mos 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 calculate_mos 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 calculate_mos. 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.
calculate_mos 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.