Generates the installation command for Starwind UI components. Validates component names and returns the correct CLI command based on the detected package manager. Use this after consulting starwind_docs to know which components to install. For Starwind Pro blocks (prefixed with @starwind-pro/), ...
AI agents use starwind_add to create or update resources in Starwind UI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starwind UI MCP Server environment.
The tool returns an installation command (write/modification operation), but the severity is low because: (1) installation commands are reversible through uninstallation, (2) the tool appears to only generate and return the command rather than directly execute it, (3) the blast radius is limited to the project dependencies being installed, which are typically expected modifications in development workflows.
From the tool's definition Generates the installation command for Starwind UI components. Validates component names and returns the correct CLI command based on the detected package manager.
Documented attack patterns abuse exactly the kind of access starwind_add 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_add:
{
"version": "1",
"default": "deny",
"tools": {
"starwind_add": {
"limits": [
{
"counter": "starwind_add_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} starwind_add 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.
Free to start. No card required.
Generates the installation command for Starwind UI components. Validates component names and returns the correct CLI command based on the detected package manager. Use this after consulting starwind_docs to know which components to install. For Starwind Pro blocks (prefixed with @starwind-pro/), set pro=true or the tool will auto-detect it. It is categorised as a Write tool in the Starwind UI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Starwind UI MCP Server MCP server in PolicyLayer and add a rule for starwind_add: 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_add 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 starwind_add 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_add. 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_add 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.