urlhaus_lookup_url
Look up URLhaus threat intelligence for exactly one HTTP(S) URL or numeric URLhaus record ID. Returns status, tags, blacklist metadata, and a bounded payload summary without contacting the reported URL.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/urlhaus-lookup-url.md
What urlhaus_lookup_url does on Livedatalink
AI agents call urlhaus_lookup_url to retrieve information from Livedatalink 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 |
|---|---|---|---|
url | string | — | HTTP(S) URL to query as an indicator, max 2048 characters. |
limit | integer | — | Maximum records to return (default 20, max 50). |
url_id | string | — | Numeric URLhaus record ID. |
Parameters from the server's own tool schema.
Why urlhaus_lookup_url is rated Low
Even though urlhaus_lookup_url 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)
Attacks that exploit this kind of access
The rule that runs urlhaus_lookup_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For urlhaus_lookup_url, this is the rule to start with:
urlhaus_lookup_url 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 Livedatalink, apply this rule, and every urlhaus_lookup_url call is checked against it from then on.
Questions about urlhaus_lookup_url
Look up URLhaus threat intelligence for exactly one HTTP(S) URL or numeric URLhaus record ID. Returns status, tags, blacklist metadata, and a bounded payload summary without contacting the reported URL. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
urlhaus_lookup_url accepts 3 parameters: url, limit, url_id. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for urlhaus_lookup_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 Livedatalink. Nothing to install.
urlhaus_lookup_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 urlhaus_lookup_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 urlhaus_lookup_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.
urlhaus_lookup_url is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue