Execute arbitrary SQL statements - sql="ANY_VALID_SQL" with optional parameters and transaction support. Examples: sql="CREATE INDEX ...", sql="WITH complex_cte AS (...) SELECT ...", transactional=true
Accepts freeform code/query input (sql)
Part of the PostgreSQL Database Management Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke pg_execute_sql to trigger processes or run actions in PostgreSQL Database Management Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
pg_execute_sql can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
pg_execute_sql:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full PostgreSQL Database Management Server policy for all 18 tools.
Agents calling execute-class tools like pg_execute_sql have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
pg_execute_sql is one of the high-risk operations in PostgreSQL Database Management Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Execute arbitrary SQL statements - sql="ANY_VALID_SQL" with optional parameters and transaction support. Examples: sql="CREATE INDEX ...", sql="WITH complex_cte AS (...) SELECT ...", transactional=true. It is categorised as a Execute tool in the PostgreSQL Database Management Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for pg_execute_sql. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the PostgreSQL Database Management Server MCP server.
pg_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 pg_execute_sql rule in your Intercept 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 Intercept policy for pg_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.
pg_execute_sql is provided by the PostgreSQL Database Management Server MCP server (HenkDz/postgresql-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept