失陷检测：检测IP地址或域名的恶意威胁，识别远控(C2)、恶意软件、矿池等威胁
AI agents call ioc_detection to retrieve information from ThreatMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs IOC (Indicator of Compromise) detection by querying threat intelligence data about IP addresses or domains. It identifies malicious threats such as C2 infrastructure, malware, and mining pools. This is a read-only lookup operation with no side effects — it retrieves and returns threat classification data without modifying any systems.
From the tool's definition 失陷检测：检测IP地址或域名的恶意威胁，识别远控(C2)、恶意软件、矿池等威胁 — 'detects' and 'identifies' threats, indicating a read/query operation against threat intelligence data
Documented attack patterns abuse exactly the kind of access ioc_detection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThreatMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ioc_detection:
{
"version": "1",
"default": "deny",
"tools": {
"ioc_detection": {}
}
}ioc_detection 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.
失陷检测：检测IP地址或域名的恶意威胁，识别远控(C2)、恶意软件、矿池等威胁. It is categorised as a Read tool in the ThreatMCP MCP Server, which means it retrieves data without modifying state.
Register the Threat MCP server in PolicyLayer and add a rule for ioc_detection: 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 ThreatMCP. Nothing to install.
ioc_detection 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 ioc_detection 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 ioc_detection. 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.
ioc_detection is provided by the Threat MCP server (naxg/threatmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThreatMCP, 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.
15 ThreatMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.