Check a given IP address against URLhaus blacklist for IOCs
AI agents call check_ip_threats to retrieve information from WireMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only check of an IP address against a public blacklist database. No data is created, modified, deleted, or executed as a result of this operation. While it is part of a network security analysis suite, the specific function is purely informational: it queries existing threat intelligence indicators without side effects.
From the tool's definition Tool description states 'Check a given IP address against URLhaus blacklist' — this is a lookup/query operation that retrieves threat intelligence data without modifying it, making no external changes or triggering actions beyond information retrieval.
Documented attack patterns abuse exactly the kind of access check_ip_threats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WireMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_ip_threats:
{
"version": "1",
"default": "deny",
"tools": {
"check_ip_threats": {}
}
}check_ip_threats 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 a given IP address against URLhaus blacklist for IOCs. It is categorised as a Read tool in the WireMCP MCP Server, which means it retrieves data without modifying state.
Register the Wire MCP server in PolicyLayer and add a rule for check_ip_threats: 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 WireMCP. Nothing to install.
check_ip_threats 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_ip_threats 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_ip_threats. 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_ip_threats is provided by the Wire MCP server (0xkoda/wiremcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 WireMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 WireMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.