# check_ip_threats

Check a given IP address against URLhaus blacklist for IOCs

Agent View of the PolicyLayer registry record for `check_ip_threats`. HTML page: https://policylayer.com/tools/0xkoda-wiremcp/check-ip-threats

## Facts

- Tool: `check_ip_threats`
- Server: WireMCP (`0xkoda/wiremcp`) — https://policylayer.com/tools/0xkoda-wiremcp.md
- Homepage: https://github.com/0xKoda/WireMCP
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_ip_threats",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches WireMCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_ip_threats": {}
  }
}
```

## Other tools on WireMCP (6)

- `capture_packets` — Execute — https://policylayer.com/tools/0xkoda-wiremcp/capture-packets.md
- `get_summary_stats` — Execute — https://policylayer.com/tools/0xkoda-wiremcp/get-summary-stats.md
- `analyze_pcap` — Read — https://policylayer.com/tools/0xkoda-wiremcp/analyze-pcap.md
- `check_threats` — Read — https://policylayer.com/tools/0xkoda-wiremcp/check-threats.md
- `extract_credentials` — Read — https://policylayer.com/tools/0xkoda-wiremcp/extract-credentials.md
- `get_conversations` — Read — https://policylayer.com/tools/0xkoda-wiremcp/get-conversations.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xkoda-wiremcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xkoda-wiremcp