Builds a site from a Stitch project by mapping screens to routes. Returns the design HTML for each page to use as context for code generation.
AI agents invoke build_site to trigger actions in Stitch MCP Server. 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.
This tool executes a site-building workflow with dependencies on project structure and configuration. While it does not directly delete data (ruling out Destructive) or write persistent changes to the design system itself (Write alone is insufficient), it orchestrates external build/compilation operations whose success or failure depends on provided arguments and project state.
From the tool's definition Tool 'builds a site' and 'maps screens to routes' — it performs compilation/generation operations that trigger external effects (site construction, route mapping).
Attacks that exploit this kind of access
Builds a site from a Stitch project by mapping screens to routes. Returns the design HTML for each page to use as context for code generation. It is categorised as a Execute tool in the Stitch MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Stitch MCP Server MCP server in PolicyLayer and add a rule for build_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 Stitch MCP Server. Nothing to install.
build_site 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 build_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 build_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.
build_site is provided by the Stitch MCP Server MCP server (oogleyskr/stitch-mcp-server). 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 →