check_ip_threats
Check a given IP address against URLhaus blacklist for IOCs
This record as markdown: /tools/0xkoda-wiremcp/check-ip-threats.md
What check_ip_threats does on WireMCP
AI agents call check_ip_threats to retrieve information from WireMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_ip_threats is rated Low
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.
Attacks that exploit this kind of access
The rule that runs check_ip_threats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WireMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_ip_threats, this is the rule to start with:
check_ip_threats 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 WireMCP, apply this rule, and every check_ip_threats call is checked against it from then on.
Questions about check_ip_threats
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.
More on Wire, and thousands of servers like it.
This server
Across the catalogue