json_schema_infer
Infer a JSON Schema (draft 2020-12) from one JSON document or many samples: types (integer vs number), nested objects and arrays, required keys (present in every sample), nullable fields, string formats (date-time, date, email, uri, uuid, ipv4/6) and optionally enums and numeric bounds. Turns API...
This record as markdown: /tools/com-it-scorptech-x402/json-schema-infer.md
What json_schema_infer does on ScorpTech x402 API
AI agents call json_schema_infer 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 |
|---|---|---|---|
json | object | — | One JSON document |
enums | boolean | — | Emit enum for low-cardinality repeated strings |
title | string | — | |
bounds | boolean | — | Emit minimum/maximum for numbers |
samples | array | — | Several sample documents of the same shape (better required/nullable detection) |
Parameters from the server's own tool schema.
Why json_schema_infer is rated Low
Even though json_schema_infer 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 json_schema_infer 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 json_schema_infer, this is the rule to start with:
json_schema_infer 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 json_schema_infer call is checked against it from then on.
Questions about json_schema_infer
Infer a JSON Schema (draft 2020-12) from one JSON document or many samples: types (integer vs number), nested objects and arrays, required keys (present in every sample), nullable fields, string formats (date-time, date, email, uri, uuid, ipv4/6) and optionally enums and numeric bounds. Turns API responses into a contract for validation or tool definitions. POST JSON body. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/json-schema-infer. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
json_schema_infer accepts 5 parameters: json, enums, title, bounds, samples. 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 json_schema_infer: 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.
json_schema_infer 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 json_schema_infer 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 json_schema_infer. 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.
json_schema_infer 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