deploy_site
Re-render the project
This record as markdown: /tools/ai-featureboard-featureboard/deploy-site.md
What deploy_site does on FeatureBoard
AI agents invoke deploy_site to trigger actions in FeatureBoard. 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.
Why deploy_site is rated High
This tool executes a deployment operation ('re-render the project'), which modifies the live state of a website/project. It is an Execute category tool because it triggers an external operation whose effects depend on the current project state. While 'rendering' alone might sound benign, in the context of a project board deployed to production, this constitutes triggering a build/deployment pipeline.
From the tool's definition Tool name 'deploy_site' combined with description 're-render the project' indicates execution of a deployment/rendering operation that triggers external systems and cannot be fully reversed without manual intervention.
Attacks that exploit this kind of access
The rule that runs deploy_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 deploy_site, this is the rule to start with:
deploy_site stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 deploy_site call is checked against it from then on.
Questions about deploy_site
Re-render the project. It is categorised as a Execute tool in the FeatureBoard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for deploy_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.
deploy_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 deploy_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 deploy_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.
deploy_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.
Across the catalogue