ip_range_merge
Aggregate IP allow/deny lists: merges any mix of IPv4/IPv6 addresses, CIDRs, "a-b" ranges and "ip netmask" entries into the minimal set of CIDR blocks, optionally subtracts an exclude list, reports address counts and tests IPs for membership. For firewall rules, WAF / CDN allowlists and cloud sec...
This record as markdown: /tools/com-it-scorptech-x402/ip-range-merge.md
What ip_range_merge does on ScorpTech x402 API
AI agents use ip_range_merge to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
check | array | — | IPs to test against the merged result |
items | array | Yes | |
exclude | array | — |
Parameters from the server's own tool schema.
Why ip_range_merge is rated Medium
An AI agent can call ip_range_merge faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs ip_range_merge 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_range_merge, this is the rule to start with:
ip_range_merge stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every ip_range_merge call is checked against it from then on.
Questions about ip_range_merge
Aggregate IP allow/deny lists: merges any mix of IPv4/IPv6 addresses, CIDRs, "a-b" ranges and "ip netmask" entries into the minimal set of CIDR blocks, optionally subtracts an exclude list, reports address counts and tests IPs for membership. For firewall rules, WAF / CDN allowlists and cloud security groups. POST JSON body {items, exclude?, check?}. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/ip-range-merge. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ip_range_merge accepts 3 parameters: check, items, exclude. Required: items. 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_range_merge: 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_range_merge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ip_range_merge 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_range_merge. 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_range_merge 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.
This server
Across the catalogue