IP分析：全面分析IP地址，包括地理位置、ASN、威胁情报、相关样本、端口信息等
AI agents call ip_analysis 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 retrieves and queries threat intelligence data about an IP address — geolocation, ASN, threat info, related samples, and port data. It performs read-only lookups with no side effects, writes, or destructive actions.
From the tool's definition 全面分析IP地址，包括地理位置、ASN、威胁情报、相关样本、端口信息等 (Comprehensive analysis of IP address including geolocation, ASN, threat intelligence, related samples, port information)
Documented attack patterns abuse exactly the kind of access ip_analysis 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 ip_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"ip_analysis": {}
}
}ip_analysis 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分析：全面分析IP地址，包括地理位置、ASN、威胁情报、相关样本、端口信息等. 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 ip_analysis: 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.
ip_analysis 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 ip_analysis 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 ip_analysis. 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.
ip_analysis 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.