AI agents call render_list_deploys to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
api_key | string | — | |
service_id | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves and displays deployment information for a Render service. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is a straightforward informational query, making it a Read category tool with low severity since listing past deploys poses minimal risk even if misused by an agent.
From the tool's definition 'List deploys for a Render service' — the verb 'list' indicates a read-only retrieval operation that queries deployment history without modifying or executing anything.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List deploys for a Render service. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
render_list_deploys accepts 3 parameters: limit, api_key, service_id. Required: service_id. 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_deploys: 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_deploys 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_deploys 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_deploys. 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_deploys 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →