equity_onboarding_start
Opens a company's proof-of-formation intake so its cap table can be set up. Idempotent: a company has at most one open intake, and calling again returns the existing one rather than splitting the answers across two records. Safe to call first when you do not know whether an intake exists.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/equity-onboarding-start.md
What equity_onboarding_start does on Lovie Company Formation MCP
AI agents invoke equity_onboarding_start 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 |
|---|---|---|---|
companyId | object | Yes | UUID value wrapper. |
Parameters from the server's own tool schema.
Why equity_onboarding_start is rated High
equity_onboarding_start 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 equity_onboarding_start 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 equity_onboarding_start, this is the rule to start with:
equity_onboarding_start 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 equity_onboarding_start call is checked against it from then on.
Questions about equity_onboarding_start
Opens a company's proof-of-formation intake so its cap table can be set up. Idempotent: a company has at most one open intake, and calling again returns the existing one rather than splitting the answers across two records. Safe to call first when you do not know whether an intake exists. 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.
equity_onboarding_start accepts 1 parameter: companyId. Required: companyId. 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 equity_onboarding_start: 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.
equity_onboarding_start 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 equity_onboarding_start 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 equity_onboarding_start. 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.
equity_onboarding_start 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