21 tools from the Render MCP Server, categorised by risk level.
View the Render policy →get_deploy Get details about a specific deployment 2/5 get_key_value Get details about a specific key-value instance 2/5 get_metrics Get performance metrics for a Render resource 2/5 get_postgres Get details about a specific PostgreSQL database 2/5 get_selected_workspace Get the currently selected workspace 2/5 get_service Get details about a specific service 2/5 list_deploys List deployment history for a service 2/5 list_key_value List all key-value store instances 2/5 list_log_label_values List values for a given log label 2/5 list_logs List logs matching provided filters 2/5 list_postgres_instances List all PostgreSQL databases 2/5 list_services List all services in your Render account 2/5 list_workspaces List workspaces you have access to 2/5 query_render_postgres Run a read-only SQL query against Render Postgres 3/5 create_cron_job Create a new cron job on Render 4/5 create_key_value Create a new key-value store on Render 4/5 create_postgres Create a new PostgreSQL database on Render 5/5 create_static_site Create a new static site on Render 4/5 create_web_service Create a new web service on Render 5/5 select_workspace Select a workspace to use 3/5 update_environment_variables Update all environment variables for a service 5/5 The Render MCP server exposes 21 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Render server.
Render tools are categorised as Read (14), Write (7). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept