neon_execute_sql
Execute a SQL query against a Neon database endpoint.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/neon-execute-sql.md
What neon_execute_sql does on UnClick
AI agents invoke neon_execute_sql to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | SQL query to execute |
api_key | string | — | |
branch_id | string | Yes | |
project_id | string | Yes | |
endpoint_id | string | Yes | |
database_name | string | Yes | Target database name |
Parameters from the server's own tool schema.
Why neon_execute_sql is rated High
This tool permits execution of SQL commands against a live database. While the description does not explicitly mention destructive capabilities (DELETE, DROP, etc.), SQL execution inherently includes the ability to perform reads, writes, and destructive operations depending on the query passed by the agent. The most severe potential use case governs classification.
From the tool's definition Tool name 'neon_execute_sql' and description 'Execute a SQL query against a Neon database endpoint' explicitly indicate execution of arbitrary SQL queries against a live database.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs neon_execute_sql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neon_execute_sql, this is the rule to start with:
neon_execute_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 UnClick, apply this rule, and every neon_execute_sql call is checked against it from then on.
Questions about neon_execute_sql
Execute a SQL query against a Neon database endpoint. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neon_execute_sql accepts 6 parameters: query, api_key, branch_id, project_id, endpoint_id, database_name. Required: query, branch_id, project_id, endpoint_id, database_name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for neon_execute_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 UnClick. Nothing to install.
neon_execute_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 neon_execute_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 neon_execute_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.
neon_execute_sql is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue