New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

check_url_phishing

chainpeek: Check if a URL or domain is phishing or a scam. For up to 1,000 URLs use check_urls_phishing_batch; for headers use check_security_headers. Returns whether a URL's host (or a domain) is on public phishing/scam domain lists: listed, the matched_domain, the sources that list it and share...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/check-url-phishing.md

What check_url_phishing does on Tanod

AI agents call check_url_phishing 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.

ParameterTypeRequiredDescription
url object — URL, host or domain to screen (at most 2,048 characters); only parsed, never fetched.
domain object — Alternative to url: a domain or host name.

Parameters from the server's own tool schema.

Why check_url_phishing is rated Low

Even though check_url_phishing 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.

Risk signalsAccepts URL/endpoint input (url)

Questions about check_url_phishing

What does the check_url_phishing tool do? +

chainpeek: Check if a URL or domain is phishing or a scam. For up to 1,000 URLs use check_urls_phishing_batch; for headers use check_security_headers. Returns whether a URL's host (or a domain) is on public phishing/scam domain lists: listed, the matched_domain, the sources that list it and shared_platform, with the lists' update time and a disclaimer. 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. Input that is not a URL, host or domain is a 422 invalid_input (not charged). Typically under 0.1 s (first call up to a few seconds). Price: USD 0.001. Free: 10 chain reads per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/phishing-scam-url-checker-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does check_url_phishing accept? +

check_url_phishing accepts 2 parameters: url, domain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_url_phishing? +

Register the Tanod MCP server in PolicyLayer and add a rule for check_url_phishing: 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.

What risk level is check_url_phishing? +

check_url_phishing is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_url_phishing? +

Yes. Add a rate_limit block to the check_url_phishing 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.

How do I block check_url_phishing completely? +

Set action: deny in the PolicyLayer policy for check_url_phishing. 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.

What MCP server provides check_url_phishing? +

check_url_phishing 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.