This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/netlify-list-sites.md
What netlify_list_sites does on UnClick
AI agents call netlify_list_sites 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 |
|---|---|---|---|
name | string | — | Filter sites by name |
limit | number | — | Sites to return (max 100, default 25) |
access_token | string | Yes | Netlify personal access token |
Parameters from the server's own tool schema.
Why netlify_list_sites is rated Low
This tool queries and retrieves existing Netlify site information without modifying, deleting, or executing any operations. It is a straightforward inventory/discovery operation. Severity is low because it only exposes metadata about the user's own deployed sites.
From the tool's definition Tool name includes 'list' and description states 'List Netlify sites for the account' — a read-only retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs netlify_list_sites 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_sites, this is the rule to start with:
netlify_list_sites 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_sites call is checked against it from then on.
Questions about netlify_list_sites
List Netlify sites for the account. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
netlify_list_sites accepts 3 parameters: name, limit, 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_sites: 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_sites 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_sites 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_sites. 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_sites 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