wizard_relaunch_lite
Run the first concrete Free runtime relaunch-lite wizard. It keeps preservation priorities explicit, starts with low-risk uplift, and marks the boundary where Advanced should take over.
This record as markdown: /tools/vamerli-elementify-mcp/wizard-relaunch-lite.md
What wizard_relaunch_lite does on Elementify MCP
AI agents invoke wizard_relaunch_lite to trigger actions in Elementify MCP. 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 wizard_relaunch_lite is rated High
wizard_relaunch_lite triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs wizard_relaunch_lite safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wizard_relaunch_lite, this is the rule to start with:
wizard_relaunch_lite 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 Elementify MCP, apply this rule, and every wizard_relaunch_lite call is checked against it from then on.
Questions about wizard_relaunch_lite
Run the first concrete Free runtime relaunch-lite wizard. It keeps preservation priorities explicit, starts with low-risk uplift, and marks the boundary where Advanced should take over. It is categorised as a Execute tool in the Elementify MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Elementify MCP server in PolicyLayer and add a rule for wizard_relaunch_lite: 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 Elementify MCP. Nothing to install.
wizard_relaunch_lite 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 wizard_relaunch_lite 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 wizard_relaunch_lite. 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.
wizard_relaunch_lite is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
Across the catalogue