scaffold_site
Generate a whole site in one shot from a single spec instead of set_site field-by-field: sets the home page (title, tagline, theme, sections) and creates each initial sub-page. Persisted through the website store and rendered to the site location (<project>/site/ by default, or the project
This record as markdown: /tools/ai-featureboard-featureboard/scaffold-site.md
What scaffold_site does on FeatureBoard
AI agents use scaffold_site to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why scaffold_site is rated Medium
This tool generates and persists site content (home page, sub-pages) to the file system, which is reversible data creation/modification. It does not execute arbitrary code, delete data, or move money. The severity is medium rather than low because bulk generation of site content could consume resources or overwrite existing site configurations if misused by an agent without proper safeguards.
From the tool's definition Creates or modifies data: 'Generate a whole site in one shot from a single spec', 'sets the home page', 'creates each initial sub-page', 'Persisted through the website store and rendered to the site location'
Attacks that exploit this kind of access
The rule that runs scaffold_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scaffold_site, this is the rule to start with:
scaffold_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every scaffold_site call is checked against it from then on.
Questions about scaffold_site
Generate a whole site in one shot from a single spec instead of set_site field-by-field: sets the home page (title, tagline, theme, sections) and creates each initial sub-page. Persisted through the website store and rendered to the site location (<project>/site/ by default, or the project. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for scaffold_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 FeatureBoard. Nothing to install.
scaffold_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scaffold_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 scaffold_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.
scaffold_site is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue