This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/netlify-get-site.md
What netlify_get_site does on UnClick
AI agents call netlify_get_site 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 |
|---|---|---|---|
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_get_site is rated Low
This tool retrieves/queries information about a specific Netlify site using its ID. The verb 'Get' combined with the retrieval-only semantics indicates a read-only operation with no side effects. Even if the site details included sensitive configuration, the action itself is non-destructive and reversible.
From the tool's definition Tool name 'netlify_get_site' and description 'Get a single Netlify site by id' indicates a retrieval operation with no modification or destructive capability.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs netlify_get_site 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_get_site, this is the rule to start with:
netlify_get_site 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_get_site call is checked against it from then on.
Questions about netlify_get_site
Get a single Netlify site by id. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
netlify_get_site accepts 2 parameters: 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_get_site: 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_get_site 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_get_site 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_get_site. 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_get_site 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