render_trigger_deploy
Trigger a new deploy for a Render service.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/render-trigger-deploy.md
What render_trigger_deploy does on UnClick
AI agents invoke render_trigger_deploy to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
service_id | string | Yes | |
clear_cache | boolean | — | Clear build cache before deploying |
Parameters from the server's own tool schema.
Why render_trigger_deploy is rated High
This tool triggers deployment operations on Render, an external hosting platform. While deployments themselves are not inherently destructive, they execute code in production and can cause service outages, data loss, or security issues depending on what is deployed. This makes it an Execute-category tool with high severity due to the potential blast radius of a misconfigured or malicious deployment.
From the tool's definition The tool description states it will "Trigger a new deploy for a Render service." This directly executes an external operation (deployment) whose effects are determined by the service configuration and cannot be easily undone if the deployment causes issues.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs render_trigger_deploy 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_trigger_deploy, this is the rule to start with:
render_trigger_deploy stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_trigger_deploy call is checked against it from then on.
Questions about render_trigger_deploy
Trigger a new deploy for a Render service. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
render_trigger_deploy accepts 3 parameters: api_key, service_id, clear_cache. 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_trigger_deploy: 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_trigger_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the render_trigger_deploy 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_trigger_deploy. 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_trigger_deploy 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.
Across the catalogue