cap_table_record_cap_table_investment

Records one holding end-to-end: resolves or creates the stakeholder, then creates the holding with all derived fields, attaching or auto-creating a round for SAFE/Preferred. SAFE requires a valuation_cap. VESTING: for service equity held by a founder, employee, or advisor (instrument_type COMMON_STOCK or OPTION — restricted stock and option grants that vest over time), you MUST set the vesting field { start_date, total_months, cliff_months }. Carry these values from ExtractCapTable output (vesting_start_date / vesting_total_months / vesting_cliff_months) when importing a cap table. If such a holding has no vesting schedule in the source, ASK the user for the vesting start date, total months (e.g. 48), and cliff months (e.g. 12) BEFORE calling this tool — do not omit vesting and do not silently record it as fully vested. OMIT vesting entirely for investor instruments (SAFE, PREFERRED_STOCK, CONVERTIBLE_NOTE) — they never vest. Returns the stakeholder, security, and round ids. The response carries the cap table before this call, what it added, and the cap table after — report an import in exactly that order (current table, new additions, final table) and take the totals from the response rather than reading the cap table again. For several SAFEs at once, list every one you are about to add and get a yes before the first call, not after the last. PARTY: pass stakeholder_id whenever the person or fund is ALREADY on the cap table — including one you created or recorded earlier in this same conversation, and one you just read from GetListCapTableStakeholders. Use new_stakeholder ONLY for a party that is not on the register yet. Re-sending a name you have already used adds a SECOND row for the same person: the twin holds no equity, so ownership views hide it while stakeholder counts include it, and the register then disagrees with itself. If you are not certain whether a party exists, call GetListCapTableStakeholders first and take the id from there. The response returns stakeholder_reused — when it is true, say the holding was added to the existing stakeholder, never that a new one was created. 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.

cap_table_record_cap_table_investment accepts 12 parameters: mfn, shares, proRata, roundId, vesting, safeType, companyId, signedDate, discountRate, valuationCap, stakeholderId, instrumentType. 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 cap_table_record_cap_table_investment: 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.

cap_table_record_cap_table_investment 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 cap_table_record_cap_table_investment 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 cap_table_record_cap_table_investment. 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.

cap_table_record_cap_table_investment 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.