This record as markdown: /tools/io-github-devopam-mcpg/translate-nl-to-sql.md
What translate_nl_to_sql does on Mcpg
AI agents invoke translate_nl_to_sql to trigger actions in Mcpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why translate_nl_to_sql is rated High
The tool name implies translating natural language to SQL, which would then likely be executed against a PostgreSQL database. Given the sibling tools (query plan analysis, compression policies, retention policies, etc.) on a production PostgreSQL server, this tool almost certainly generates and/or executes arbitrary SQL.
From the tool's definition Tool name 'translate_nl_to_sql' on a production-grade PostgreSQL MCP server; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs translate_nl_to_sql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For translate_nl_to_sql, this is the rule to start with:
translate_nl_to_sql stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every translate_nl_to_sql call is checked against it from then on.
Questions about translate_nl_to_sql
translate_nl_to_sql is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpg MCP server in PolicyLayer and add a rule for translate_nl_to_sql: 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 Mcpg. Nothing to install.
translate_nl_to_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the translate_nl_to_sql 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 translate_nl_to_sql. 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.
translate_nl_to_sql is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue