Low Risk

check_controlled_substance

Check international controlled-substance scheduling status across UN, EU, and novel psychoactive substance databases. Input: substance name, cannabinoid, narcotic drug, precursor, NPS name, synonym, or CAS number (e.g. 'cannabis', 'THC', 'morphine', 'pseudoephedrine', '64-17-5'). Returns: UN INCB...

Risk signalsAccepts freeform code/query input (query)

Part of the Cannabis Regulatory server.

check_controlled_substance 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 CANNABIS REGULATORY →

Free to start. No card required.

AI agents call check_controlled_substance to retrieve information from Cannabis 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_controlled_substance 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": {
    "check_controlled_substance": {}
  }
}

See the full Cannabis Regulatory policy for all 4 tools.

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

ENFORCE ON MY CANNABIS REGULATORY →

These attack patterns abuse exactly the kind of access check_controlled_substance 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 check_controlled_substance only ever does what you allow.

SECURE CANNABIS REGULATORY →

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

What does the check_controlled_substance tool do? +

Check international controlled-substance scheduling status across UN, EU, and novel psychoactive substance databases. Input: substance name, cannabinoid, narcotic drug, precursor, NPS name, synonym, or CAS number (e.g. 'cannabis', 'THC', 'morphine', 'pseudoephedrine', '64-17-5'). Returns: UN INCB Yellow List scheduling (narcotic drugs under 1961 Single Convention — schedule, synonyms, formula, conversion ratio, CAS), EU Drug Precursor category (CN code, threshold quantities, license/registration requirements), and EMCDDA/EUDA Novel Psychoactive Substance risk assessment (chemical class, control status, risk assessment year, scheduling decision). Sources: INCB Yellow List (154 narcotic drugs), EU Drug Precursors regulation (46 chemicals), EMCDDA/EUDA NPS risk assessments (41 substances). For controlled substance regulatory compliance and scheduling verification. Do not use for cannabis testing limits (use check_cannabis_testing) or product compliance summaries (use check_cannabis_compliance).. It is categorised as a Read tool in the Cannabis Regulatory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_controlled_substance? +

Register the Cannabis Regulatory MCP server in PolicyLayer and add a rule for check_controlled_substance: 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 Cannabis Regulatory. Nothing to install.

What risk level is check_controlled_substance? +

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

Can I rate-limit check_controlled_substance? +

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

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

check_controlled_substance is provided by the Cannabis Regulatory MCP server (https://cannabis-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.

Enforce policy on every Cannabis Regulatory tool call.

Deterministic rules across all 4 Cannabis 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.