sql_format
Format and lint SQL: consistent keyword case, one clause per line, indented select lists, joins, AND/OR conditions and subqueries, comments and string literals preserved; or minify. The linter flags UPDATE/DELETE without WHERE, SELECT *, implicit comma joins, leading-wildcard LIKE, ORDER BY RAND(...
This record as markdown: /tools/com-it-scorptech-x402/sql-format.md
What sql_format does on ScorpTech x402 API
AI agents call sql_format to permanently remove resources in ScorpTech x402 API, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
sql | string | Yes | |
indent | integer | — | |
minify | boolean | — | |
keywordCase | string | — |
Parameters from the server's own tool schema.
Why sql_format is rated Critical
An AI agent that decides to call sql_format doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ScorpTech x402 API is gone. There is no undo for destructive operations.
Risk signalsAccepts freeform code/query input (sql)
Attacks that exploit this kind of access
The rule that runs sql_format 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 sql_format, this is the rule to start with:
sql_format is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every sql_format call is checked against it from then on.
Questions about sql_format
Format and lint SQL: consistent keyword case, one clause per line, indented select lists, joins, AND/OR conditions and subqueries, comments and string literals preserved; or minify. The linter flags UPDATE/DELETE without WHERE, SELECT *, implicit comma joins, leading-wildcard LIKE, ORDER BY RAND(), NOT IN with subqueries and string-concatenation injection smells, and lists statement types and referenced tables. POST JSON body {sql}. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/sql-format. It is categorised as a Destructive tool in the ScorpTech x402 API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
sql_format accepts 4 parameters: sql, indent, minify, keywordCase. Required: sql. 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 sql_format: 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.
sql_format is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sql_format 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 sql_format. 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.
sql_format 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.
Across the catalogue