Retrieve US state-level cannabis testing limits and action levels for regulatory compliance. Input: US state name (e.g. 'California', 'Colorado'), optional test category (pesticide, heavy_metal, microbial, solvent, mycotoxin, potency, moisture), and optional specific analyte name (e.g. 'lead', 'a...
Part of the Cannabis Regulatory server.
Free to start. No card required.
AI agents call check_cannabis_testing 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_cannabis_testing 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_cannabis_testing": {}
}
}See the full Cannabis Regulatory policy for all 4 tools.
These attack patterns abuse exactly the kind of access check_cannabis_testing 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.
Retrieve US state-level cannabis testing limits and action levels for regulatory compliance. Input: US state name (e.g. 'California', 'Colorado'), optional test category (pesticide, heavy_metal, microbial, solvent, mycotoxin, potency, moisture), and optional specific analyte name (e.g. 'lead', 'arsenic', 'Salmonella', 'butane'). Returns: testing categories with analyte names, action levels (pass/fail thresholds), units (ppm, ppb, CFU/g), product class applicability (flower, concentrate, edible), and regulation references. Database: 1,942 state-level testing requirements across all legalized US states. For cannabis laboratory compliance and product testing requirements. Do not use for controlled-substance scheduling (use check_controlled_substance), Health Canada regulations (use check_cannabis_compliance with jurisdiction 'Canada'), or non-cannabis food pesticide MRLs.. It is categorised as a Read tool in the Cannabis Regulatory MCP Server, which means it retrieves data without modifying state.
Register the Cannabis Regulatory MCP server in PolicyLayer and add a rule for check_cannabis_testing: 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.
check_cannabis_testing 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_cannabis_testing 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_cannabis_testing. 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_cannabis_testing 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.
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.