check_urls_phishing_batch
chainpeek: Check up to 1,000 URLs or domains for phishing or scams in one batch. For one URL use check_url_phishing. Returns the URL check for 1-1,000 URLs, hosts or domains in one call. A screening aid: the host and its parent domains are matched against two public lists, PhishDestroy (CC0) and ...
This record as markdown: /tools/dev-tanod-tanod/check-urls-phishing-batch.md
What check_urls_phishing_batch does on Tanod
AI agents call check_urls_phishing_batch to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
items | array | Yes | 1-1,000 URLs, hosts or domains (each at most 2,048 characters); only parsed, never fetched. Priced per item. |
Parameters from the server's own tool schema.
Why check_urls_phishing_batch is rated Low
Even though check_urls_phishing_batch only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_urls_phishing_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_urls_phishing_batch, this is the rule to start with:
check_urls_phishing_batch is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every check_urls_phishing_batch call is checked against it from then on.
Questions about check_urls_phishing_batch
chainpeek: Check up to 1,000 URLs or domains for phishing or scams in one batch. For one URL use check_url_phishing. Returns the URL check for 1-1,000 URLs, hosts or domains in one call. A screening aid: the host and its parent domains are matched against two public lists, PhishDestroy (CC0) and Phishing.Database (MIT), refreshed daily; the URL is never fetched. An unlisted host is not cleared: new phishing is on no list yet, and lists can be stale. One invalid item fails the whole batch with a 422 naming its index (not charged). Typically under 1 s for 1,000 items. Price: USD 0.0002 per item, at least USD 0.001 per call (1-1,000 items per call: USD 0.001-0.2). No free tier. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/phishing-ofac-security-mcp-server.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_urls_phishing_batch accepts 1 parameter: items. Required: items. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for check_urls_phishing_batch: 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 Tanod. Nothing to install.
check_urls_phishing_batch 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_urls_phishing_batch 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_urls_phishing_batch. 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_urls_phishing_batch is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue