render_list_services
List all Render services (web services, static sites, cron jobs, etc.).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/render-list-services.md
What render_list_services does on UnClick
AI agents call render_list_services to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Filter by type: web_service, static_site, background_worker, cron_job, private_service |
limit | number | — | Max results (default 20) |
cursor | string | — | |
api_key | string | — | Render API key |
Parameters from the server's own tool schema.
Why render_list_services is rated Low
This tool retrieves and enumerates Render services metadata. It performs a query operation that returns information about existing services but does not create, modify, delete, or execute any resources. The blast radius of misuse is minimal—unauthorized enumeration could reveal service names or configurations but cannot alter infrastructure or trigger deployments.
From the tool's definition Tool name contains 'list' and description says 'List all Render services'. The verb 'list' and action of enumerating existing services indicate read-only retrieval of information without modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs render_list_services 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 render_list_services, this is the rule to start with:
render_list_services is read-only, so it stays allowed. 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 render_list_services call is checked against it from then on.
Questions about render_list_services
List all Render services (web services, static sites, cron jobs, etc.). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
render_list_services accepts 4 parameters: type, limit, cursor, api_key. 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 render_list_services: 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.
render_list_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the render_list_services 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 render_list_services. 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.
render_list_services 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.
This server
Across the catalogue