query_render_postgres

Run a read-only SQL query against Render Postgres

Part of the Render MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@render-oss/render-mcp-server Read Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents call query_render_postgres to retrieve information from Render without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON QUERY_RENDER_POSTGRES

Even though query_render_postgres only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

render.yaml

tools:
  query_render_postgres:
    rules:
      - action: allow

See the full Render policy for all 21 tools.

// DETAILS

Tool Name query_render_postgres

Category Read

MCP Server Render MCP Server

Risk Level Low

// MORE RENDER TOOLS

Write create_cron_job Write create_key_value Write create_postgres Write create_static_site Write create_web_service Write select_workspace Write update_environment_variables Read get_deploy

View all 21 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like query_render_postgres have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the query_render_postgres tool do? +

Run a read-only SQL query against Render Postgres. It is categorised as a Read tool in the Render MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_render_postgres? +

Add a rule in your Intercept YAML policy under the tools section for query_render_postgres. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Render MCP server.

What risk level is query_render_postgres? +

query_render_postgres is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_render_postgres? +

Yes. Add a rate_limit block to the query_render_postgres 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.

How do I block query_render_postgres completely? +

Set action: deny in the Intercept policy for query_render_postgres. 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.

What MCP server provides query_render_postgres? +

query_render_postgres is provided by the Render MCP server (@render-oss/render-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

query_render_postgres

Enforce policies on Render