sql_format
Format/beautify SQL queries with configurable dialect.
This record as markdown: /tools/io-github-scotia1973-bot-api-hub/sql-format.md
What sql_format does on GadgetHumans API Hub
AI agents call sql_format to retrieve information from GadgetHumans API Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sql_format is rated Low
This tool formats/beautifies SQL queries — it is a text transformation utility that takes SQL as input and returns a formatted version. It does not execute, store, or transmit the SQL to any database. No side effects beyond returning transformed text, making it a Read/utility operation. Low severity because misuse risk is minimal; it cannot execute queries or affect any data store.
From the tool's definition Format/beautify SQL queries with configurable dialect
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 GadgetHumans API Hub, 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 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 GadgetHumans API Hub, apply this rule, and every sql_format call is checked against it from then on.
Questions about sql_format
Format/beautify SQL queries with configurable dialect. It is categorised as a Read tool in the GadgetHumans API Hub MCP Server, which means it retrieves data without modifying state.
Register the GadgetHumans API Hub 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 GadgetHumans API Hub. Nothing to install.
sql_format 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 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 GadgetHumans API Hub MCP server (pypi:gadgethumans-api-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GadgetHumans API Hub, and thousands of servers like it.
This server
Across the catalogue