cidr_calc
IPv4 / IPv6 subnet calculator: network and broadcast/last address, netmask, wildcard, first/last usable host, address and host counts, address type (private, CGNAT, documentation, ULA, link-local...), reverse-DNS zone, expanded/compressed IPv6; check whether IPs fall inside, and split the block i...
This record as markdown: /tools/com-it-scorptech-x402/cidr-calc.md
What cidr_calc does on ScorpTech x402 API
AI agents call cidr_calc to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cidr | string | Yes | e.g. 10.0.0.0/8, 2001:db8::/48, "192.168.1.0 255.255.255.0" |
contains | array | — | IPs to test for membership |
splitPrefix | integer | — | Split into subnets of this prefix length (first 256 listed) |
Parameters from the server's own tool schema.
Why cidr_calc is rated Low
Even though cidr_calc only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs cidr_calc 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 cidr_calc, this is the rule to start with:
cidr_calc is read-only, so it stays allowed. 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 cidr_calc call is checked against it from then on.
Questions about cidr_calc
IPv4 / IPv6 subnet calculator: network and broadcast/last address, netmask, wildcard, first/last usable host, address and host counts, address type (private, CGNAT, documentation, ULA, link-local...), reverse-DNS zone, expanded/compressed IPv6; check whether IPs fall inside, and split the block into smaller subnets. Accepts CIDR, "ip netmask" or a single IP. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/cidr-calc. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
cidr_calc accepts 3 parameters: cidr, contains, splitPrefix. Required: cidr. 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 cidr_calc: 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.
cidr_calc 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 cidr_calc 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 cidr_calc. 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.
cidr_calc 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