Low Risk

calculate_mos

Use this tool when the user needs a Margin of Safety (MoS) calculation for cosmetic safety assessment, CPSR (Cosmetic Product Safety Report) documentation, or regulatory submission under SCCS Notes of Guidance (SCCS/1647/22) methodology. Computes SED (Systemic Exposure Dose, mg/kg bw/day) from NO...

Part of the Cosmetic Regulatory Intelligence server.

calculate_mos 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 COSMETIC REGULATORY INTELLIGENCE →

Free to start. No card required.

AI agents call calculate_mos to retrieve information from Cosmetic Regulatory Intelligence 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "calculate_mos": {}
  }
}

See the full Cosmetic Regulatory Intelligence policy for all 4 tools.

Get this rule live on your own Cosmetic Regulatory Intelligence server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COSMETIC REGULATORY INTELLIGENCE →

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:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so calculate_mos only ever does what you allow.

SECURE COSMETIC REGULATORY INTELLIGENCE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the calculate_mos tool do? +

Use this tool when the user needs a Margin of Safety (MoS) calculation for cosmetic safety assessment, CPSR (Cosmetic Product Safety Report) documentation, or regulatory submission under SCCS Notes of Guidance (SCCS/1647/22) methodology. Computes SED (Systemic Exposure Dose, mg/kg bw/day) from NOAEL, dermal absorption, product type exposure parameters, and use concentration, then MoS = NOAEL / SED. SCCS safety threshold is MoS > 100 for acceptable consumer risk. Returns SED, MoS value, pass/fail against SCCS-100 threshold, and full calculation trace including NOAEL source, dermal absorption basis, and SCCS exposure parameters used. Do not use for general toxicology or non-cosmetic safety margin queries — this is specifically the SCCS-methodology MoS calculation for cosmetic ingredients.. It is categorised as a Read tool in the Cosmetic Regulatory Intelligence MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calculate_mos? +

Register the Cosmetic Regulatory Intelligence 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 Intelligence. Nothing to install.

What risk level is calculate_mos? +

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

Can I rate-limit calculate_mos? +

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.

How do I block calculate_mos completely? +

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.

What MCP server provides calculate_mos? +

calculate_mos is provided by the Cosmetic Regulatory Intelligence MCP server (twohalves/cosmetic-regulatory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cosmetic Regulatory Intelligence tool call.

Deterministic rules across all 4 Cosmetic Regulatory Intelligence 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.