formation_start_formation
THE entry point for a new company formation — runs anonymously, no sign-in required. Call this DIRECTLY whenever the user wants to start, create, or form a company or formation. Do NOT call company_get_my_companies or formation_get_list_formations first; those require auth and are only for existi...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/formation-start-formation.md
What formation_start_formation does on Lovie Company Formation MCP
AI agents invoke formation_start_formation to trigger actions in Lovie Company Formation 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | |
forceNew | boolean | — | |
sessionId | object | — | UUID value wrapper. |
inviteToken | string | — | |
referralCode | string | — |
Parameters from the server's own tool schema.
Why formation_start_formation is rated High
formation_start_formation 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs formation_start_formation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lovie Company Formation MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For formation_start_formation, this is the rule to start with:
formation_start_formation 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 Lovie Company Formation MCP, apply this rule, and every formation_start_formation call is checked against it from then on.
Questions about formation_start_formation
THE entry point for a new company formation — runs anonymously, no sign-in required. Call this DIRECTLY whenever the user wants to start, create, or form a company or formation. Do NOT call company_get_my_companies or formation_get_list_formations first; those require auth and are only for existing records — starting a new formation needs neither. Returns a formation_id plus the ordered steps. Calling it again for the same signed-in user RESUMES the formation already in progress and returns its id with resumed=true — it does not create a second one, so a retry is safe. When resumed=true, tell the user which company you are continuing (the response carries its name) instead of assuming it is the one they just described. If they say they want a DIFFERENT, additional company, call again with force_new=true — that is the only time to set it; never set it to retry. Before walking the steps, briefly understand the user's business, experience, and funding (one question at a time), then give a tailored recommendation. Keep the formation_id and pass it to every later step. Call this exactly ONCE per formation — never start a second one to resume. When a later step needs sign-in, let the user connect and retry with the SAME formation_id; signing in automatically claims the in-progress formation, so it is never lost. It is categorised as a Execute tool in the Lovie Company Formation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
formation_start_formation accepts 5 parameters: source, forceNew, sessionId, inviteToken, referralCode. The full parameter table on this page comes from the server's own tool schema.
Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for formation_start_formation: 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 Lovie Company Formation MCP. Nothing to install.
formation_start_formation 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 formation_start_formation 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 formation_start_formation. 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.
formation_start_formation is provided by the Lovie Company Formation MCP server (lovie). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lovie Company Formation, and thousands of servers like it.
Across the catalogue