urlhaus_recent
Get recent malware URLs added to the URLhaus database.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/urlhaus-recent.md
What urlhaus_recent does on UnClick
AI agents call urlhaus_recent to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why urlhaus_recent is rated Low
This tool retrieves publicly available threat intelligence data from URLhaus without modifying, deleting, or executing anything. It is a read-only operation that queries a database of known malicious URLs. While the data retrieved pertains to malware, the tool itself performs no destructive, financial, or execution-based actions.
From the tool's definition Tool name 'urlhaus_recent' and description 'Get recent malware URLs added to the URLhaus database' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs urlhaus_recent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For urlhaus_recent, this is the rule to start with:
urlhaus_recent 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 UnClick, apply this rule, and every urlhaus_recent call is checked against it from then on.
Questions about urlhaus_recent
Get recent malware URLs added to the URLhaus database. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for urlhaus_recent: 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 UnClick. Nothing to install.
urlhaus_recent 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_recent 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_recent. 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_recent is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue