Check if a Bitcoin address is associated with a known ransomware family using the Ransomwhere database. Args: bitcoin_address: Bitcoin wallet address to look up (P2PKH, P2SH, or bech32)
AI agents call check_ransomware_intel to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query against a threat intelligence database (Ransomwhere) to retrieve correlation data about Bitcoin addresses. It retrieves existing information without side effects, modifications, or system impact. The severity is low because the tool only returns intelligence data about an address; misuse cannot directly harm systems, delete data, execute code, or move funds.
From the tool's definition Tool name 'check_ransomware_intel' and description indicate it 'Check[s] if a Bitcoin address is associated with a known ransomware family using the Ransomwhere database.' This is a lookup/query operation that retrieves intelligence data without modifying,…
Documented attack patterns abuse exactly the kind of access check_ransomware_intel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_ransomware_intel:
{
"version": "1",
"default": "deny",
"tools": {
"check_ransomware_intel": {}
}
}check_ransomware_intel is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a Bitcoin address is associated with a known ransomware family using the Ransomwhere database. Args: bitcoin_address: Bitcoin wallet address to look up (P2PKH, P2SH, or bech32). It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE MCP Server MCP server in PolicyLayer and add a rule for check_ransomware_intel: 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 CVE MCP Server. Nothing to install.
check_ransomware_intel 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_ransomware_intel 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_ransomware_intel. 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_ransomware_intel is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CVE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.