Initializes a Starwind UI project. ALWAYS use this tool FIRST before adding any Starwind components or blocks. Defaults to Pro setup (recommended) which enables both standard components AND Pro blocks. Set pro=false only if you specifically want standard-only setup.
AI agents invoke starwind_init to trigger actions in Starwind UI 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.
Project initialization triggers external operations such as creating config files, modifying package.json, installing dependencies, and setting up project scaffolding. This goes beyond a simple write — it executes a setup process that affects the project environment and file system in ways that depend on the arguments (e.g., pro=false). Misuse by an AI agent could corrupt or reconfigure a project unexpectedly.
From the tool's definition Initializes a Starwind UI project... ALWAYS use this tool FIRST before adding any Starwind components or blocks
Documented attack patterns abuse exactly the kind of access starwind_init gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Starwind UI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for starwind_init:
{
"version": "1",
"default": "deny",
"tools": {
"starwind_init": {
"limits": [
{
"counter": "starwind_init_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}starwind_init 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.
Free to start. No card required.
Initializes a Starwind UI project. ALWAYS use this tool FIRST before adding any Starwind components or blocks. Defaults to Pro setup (recommended) which enables both standard components AND Pro blocks. Set pro=false only if you specifically want standard-only setup. It is categorised as a Execute tool in the Starwind UI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Starwind UI MCP Server MCP server in PolicyLayer and add a rule for starwind_init: 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 Starwind UI MCP Server. Nothing to install.
starwind_init 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 starwind_init 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 starwind_init. 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.
starwind_init is provided by the Starwind UI MCP Server MCP server (starwind-ui/starwind-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Starwind UI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Starwind UI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.