Start a cookie consent compliance scan on the given URL. The scan runs asynchronously in the background. This tool returns a run_id immediately — the actual scan takes 60–120 seconds. Use get_scan_status(run_id) to poll for completion, then call get_scan_report(run_id) or get_failing_checks(run_id).
Risk signalsAccepts URL/endpoint input (url)
Part of the Cookie Consent Compliance Scanner server.
Free to start. No card required.
AI agents call scan_url to retrieve information from Cookie Consent Compliance Scanner 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 scan_url 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": {
"scan_url": {}
}
}See the full Cookie Consent Compliance Scanner policy for all 5 tools.
These attack patterns abuse exactly the kind of access scan_url 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.
Start a cookie consent compliance scan on the given URL. The scan runs asynchronously in the background. This tool returns a run_id immediately — the actual scan takes 60–120 seconds. Use get_scan_status(run_id) to poll for completion, then call get_scan_report(run_id) or get_failing_checks(run_id).. It is categorised as a Read tool in the Cookie Consent Compliance Scanner MCP Server, which means it retrieves data without modifying state.
Register the Cookie Consent Compliance Scanner MCP server in PolicyLayer and add a rule for scan_url: 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 Cookie Consent Compliance Scanner. Nothing to install.
scan_url 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 scan_url 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 scan_url. 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.
scan_url is provided by the Cookie Consent Compliance Scanner MCP server (https://consent-analyser-emea.waivern.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Cookie Consent Compliance Scanner 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.