float_order
IEEE 754 totalOrder on two binary32 or binary64 values. Negative zero is below positive zero. Negative NaNs are below minus infinity and positive NaNs are above plus infinity. A larger NaN payload is farther from zero. sameBits is true only when every bit matches. form bits reads both sides as he...
This record as markdown: /tools/com-it-scorptech-x402/float-order.md
What float_order does on ScorpTech x402 API
AI agents call float_order 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 |
|---|---|---|---|
form | string | — | |
left | string | Yes | |
right | string | Yes | |
width | integer | — |
Parameters from the server's own tool schema.
Why float_order is rated Low
Even though float_order 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs float_order 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 float_order, this is the rule to start with:
float_order 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 float_order call is checked against it from then on.
Questions about float_order
IEEE 754 totalOrder on two binary32 or binary64 values. Negative zero is below positive zero. Negative NaNs are below minus infinity and positive NaNs are above plus infinity. A larger NaN payload is farther from zero. sameBits is true only when every bit matches. form bits reads both sides as hex; the default reads them as numbers rounded ties-to-even. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/float-order. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
float_order accepts 4 parameters: form, left, right, width. Required: left, right. 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 float_order: 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.
float_order 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 float_order 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 float_order. 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.
float_order 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