Get details of a specific site
AI agents call getSite to retrieve information from Netlify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about a Netlify site without creating, modifying, or deleting any data. It is a straightforward read operation that returns site metadata. While the server includes destructive tools (deleteSite) and write operations (createSiteFromGitHub), this particular tool is limited to querying existing data, which carries minimal risk of misuse.
From the tool's definition Tool name 'getSite' and description 'Get details of a specific site' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific site. It is categorised as a Read tool in the Netlify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Netlify MCP Server MCP server in PolicyLayer and add a rule for getSite: 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 Netlify MCP Server. Nothing to install.
getSite 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 getSite 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 getSite. 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.
getSite is provided by the Netlify MCP Server MCP server (mcerqua/netlify-mcp). 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 →