Analyze a URL for security threats with optional user intent context (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and intent_alignment. For long-running scans, prefer url_scanner_async_scan_with_intent which returns immediately with a tas...
Accepts URL/endpoint input (url)
Part of the URL security scanner to protect AI agent workflows MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call url_scanner_scan_with_intent to retrieve information from URL security scanner to protect AI agent workflows 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 url_scanner_scan_with_intent 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.
tools:
url_scanner_scan_with_intent:
rules:
- action: allowSee the full URL security scanner to protect AI agent workflows policy for all 6 tools.
Agents calling read-class tools like url_scanner_scan_with_intent have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Analyze a URL for security threats with optional user intent context (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and intent_alignment. For long-running scans, prefer url_scanner_async_scan_with_intent which returns immediately with a task_id for polling via url_scanner_async_task_result.. It is categorised as a Read tool in the URL security scanner to protect AI agent workflows MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for url_scanner_scan_with_intent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the URL security scanner to protect AI agent workflows MCP server.
url_scanner_scan_with_intent 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 url_scanner_scan_with_intent rule in your Intercept 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 Intercept policy for url_scanner_scan_with_intent. 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.
url_scanner_scan_with_intent is provided by the URL security scanner to protect AI agent workflows MCP server (cybrlab-ai/urlcheck-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept