6 tools from the URL security scanner to protect AI agent workflows MCP Server, categorised by risk level.
View the URL security scanner to protect AI agent workflows policy →url_scanner_async_scan Submit a URL for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, the... url_scanner_async_scan_with_intent Submit a URL with optional user intent for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_sta... url_scanner_async_task_result Retrieve the result of an asynchronous scan task. If completed, returns the full scan result (risk_score, confidence, agent_access_directive, etc.)... url_scanner_async_task_status Check the status of an asynchronous scan task. Returns the current task status using native MCP task semantics (working, completed, failed, cancell... url_scanner_scan Analyze a URL for security threats (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and inte... url_scanner_scan_with_intent Analyze a URL for security threats with optional user intent context (synchronous, blocks until complete or timeout). Returns risk score, confidenc... The URL security scanner to protect AI agent workflows MCP server exposes 6 tools across 1 categories: Read.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the URL security scanner to protect AI agent workflows server.
URL security scanner to protect AI agent workflows tools are categorised as Read (6). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept