process_json
Prettify, validate, or minify a JSON string. Use this for debugging, formatting API responses, cleaning up configuration files, or verifying that a string is valid JSON. Parameters: json_string — The JSON string to process (required). Pass the raw JSON text. mode — Operation: "prettify" (indent +...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/process-json.md
What process_json does on X402 Middleware
AI agents call process_json to retrieve information from X402 Middleware 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 |
|---|---|---|---|
mode | string | — | |
json_string | string | Yes |
Parameters from the server's own tool schema.
Why process_json is rated Low
This tool only inspects and reformats JSON strings without altering external state or data stores. It produces output based on input but makes no writes, executions, deletions, or financial transactions. The formatting and validation are purely informational operations, making it a Read-category tool with low risk.
From the tool's definition Tool performs three operations on JSON strings: prettify (indent + sort keys), validate (check syntax only), or minify (compact, no whitespace).
Attacks that exploit this kind of access
The rule that runs process_json safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For process_json, this is the rule to start with:
process_json 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 X402 Middleware, apply this rule, and every process_json call is checked against it from then on.
Questions about process_json
Prettify, validate, or minify a JSON string. Use this for debugging, formatting API responses, cleaning up configuration files, or verifying that a string is valid JSON. Parameters: json_string — The JSON string to process (required). Pass the raw JSON text. mode — Operation: "prettify" (indent + sort keys), "validate" (check syntax only), or "minify" (compact, no whitespace) (default: "prettify"). It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
process_json accepts 2 parameters: mode, json_string. Required: json_string. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for process_json: 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 X402 Middleware. Nothing to install.
process_json 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 process_json 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 process_json. 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.
process_json is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue