list_postgres_instances
List all PostgreSQL databases
Part of the Render MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call list_postgres_instances 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 LIST_POSTGRES_INSTANCES
Even though list_postgres_instances 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.
tools:
list_postgres_instances:
rules:
- action: allowSee the full Render policy for all 23 tools.
DETAILS
MORE RENDER TOOLS
list_workspaces Read get_selected_workspace Read list_services Read get_service Read list_deploys Read get_deploy Read list_logs Read list_log_label_values Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the list_postgres_instances tool do?
List all PostgreSQL databases. 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 list_postgres_instances?
Add a rule in your Intercept YAML policy under the tools section for list_postgres_instances. 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 list_postgres_instances?
list_postgres_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit list_postgres_instances?
Yes. Add a rate_limit block to the list_postgres_instances 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 list_postgres_instances completely?
Set action: deny in the Intercept policy for list_postgres_instances. 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 list_postgres_instances?
list_postgres_instances 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.
ENFORCE POLICIES ON RENDER
Open source. One binary. Zero dependencies.