inet_checksum
RFC 1071 internet checksum. Big-endian 16-bit words are added with end-around carry, then inverted. An odd final byte is padded with zero. The RFC example 0001 F203 F4F5 F6F7 is 220d. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x4...
This record as markdown: /tools/com-it-scorptech-x402/inet-checksum.md
What inet_checksum does on ScorpTech x402 API
AI agents call inet_checksum 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 |
|---|---|---|---|
hex | string | — | |
text | string | — |
Parameters from the server's own tool schema.
Why inet_checksum is rated Low
Even though inet_checksum 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 inet_checksum 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 inet_checksum, this is the rule to start with:
inet_checksum 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 inet_checksum call is checked against it from then on.
Questions about inet_checksum
RFC 1071 internet checksum. Big-endian 16-bit words are added with end-around carry, then inverted. An odd final byte is padded with zero. The RFC example 0001 F203 F4F5 F6F7 is 220d. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/inet-checksum. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
inet_checksum accepts 2 parameters: hex, text. 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 inet_checksum: 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.
inet_checksum 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 inet_checksum 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 inet_checksum. 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.
inet_checksum 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