ip_reputation
IP blocklist reputation for up to 50 IPv4/IPv6 addresses: membership in the Tor exit list, Spamhaus DROP/DROPv6, abuse.ch Feodo Tracker botnet C2 and FireHOL level1 (cached published lists), with matched range/SBL reference, categories and a simple 0-100 risk score. Blocklist membership only; com...
This record as markdown: /tools/com-it-scorptech-x402/ip-reputation.md
What ip_reputation does on ScorpTech x402 API
AI agents call ip_reputation to permanently remove resources in ScorpTech x402 API, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | Yes | One or more public IPs, comma-separated (max 50). Alias: ips |
Parameters from the server's own tool schema.
Why ip_reputation is rated Critical
An AI agent that decides to call ip_reputation doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ScorpTech x402 API is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs ip_reputation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ip_reputation, this is the rule to start with:
ip_reputation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every ip_reputation call is checked against it from then on.
Questions about ip_reputation
IP blocklist reputation for up to 50 IPv4/IPv6 addresses: membership in the Tor exit list, Spamhaus DROP/DROPv6, abuse.ch Feodo Tracker botnet C2 and FireHOL level1 (cached published lists), with matched range/SBL reference, categories and a simple 0-100 risk score. Blocklist membership only; complements /v1/ip-intel (geo/ASN). Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/ip-reputation. It is categorised as a Destructive tool in the ScorpTech x402 API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
ip_reputation accepts 1 parameter: ip. Required: ip. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for ip_reputation: 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 ScorpTech x402 API. Nothing to install.
ip_reputation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ip_reputation 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_reputation. 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_reputation is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue