netlify_list_deploys
List recent deploys for a Netlify site (signals when the latest deploy failed).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/netlify-list-deploys.md
What netlify_list_deploys does on UnClick
AI agents call netlify_list_deploys 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 |
|---|---|---|---|
limit | number | — | Deploys to return (max 100, default 10) |
site_id | string | — | Netlify site id (can be a saved default) |
access_token | string | Yes | Netlify personal access token |
Parameters from the server's own tool schema.
Why netlify_list_deploys is rated Low
This tool retrieves historical deployment data and status information from Netlify without creating, modifying, executing, or deleting anything. It is purely informational and has no side effects on the system or data. The low severity reflects minimal risk even if an AI agent misuses it — worst case would be information disclosure of deploy history visible to an authorized Netlify account.
From the tool's definition Tool name contains 'list' and description states 'List recent deploys' — a retrieval operation with no modification or execution. It only queries deploy status information ('signals when the latest deploy failed').
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs netlify_list_deploys 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 netlify_list_deploys, this is the rule to start with:
netlify_list_deploys 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 netlify_list_deploys call is checked against it from then on.
Questions about netlify_list_deploys
List recent deploys for a Netlify site (signals when the latest deploy failed). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
netlify_list_deploys accepts 3 parameters: limit, site_id, access_token. Required: access_token. 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 netlify_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.
netlify_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 netlify_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 netlify_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.
netlify_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue