cap_table_simulate_cap_table_dilution
SimulateCapTableDilution runs the SAME engine as CloseCapTableRound against the company's current stakeholders and its outstanding SAFEs, for a raise that does not exist yet — no round, nothing persisted. CALL THIS for "what happens if we raise X at Y", "model dilution", "how much do the founders...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/cap-table-simulate-cap-table-dilution.md
What cap_table_simulate_cap_table_dilution does on Lovie Company Formation MCP
AI agents call cap_table_simulate_cap_table_dilution to retrieve information from Lovie Company Formation MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | object | Yes | UUID value wrapper. |
newMoneyRaise | string | — | |
preMoneyValuation | string | — | |
targetOptionPoolPct | string | — |
Parameters from the server's own tool schema.
Why cap_table_simulate_cap_table_dilution is rated Low
Even though cap_table_simulate_cap_table_dilution only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs cap_table_simulate_cap_table_dilution 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 cap_table_simulate_cap_table_dilution, this is the rule to start with:
cap_table_simulate_cap_table_dilution is read-only, so it stays allowed. 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 cap_table_simulate_cap_table_dilution call is checked against it from then on.
Questions about cap_table_simulate_cap_table_dilution
SimulateCapTableDilution runs the SAME engine as CloseCapTableRound against the company's current stakeholders and its outstanding SAFEs, for a raise that does not exist yet — no round, nothing persisted. CALL THIS for "what happens if we raise X at Y", "model dilution", "how much do the founders keep", or any post-money ownership question. Do NOT work the answer out yourself, even when the arithmetic looks simple: two implementations of SAFE conversion produce two different founder percentages and only one of them is right, and a hand-computed cap table presented as fact is the failure this tool exists to prevent. It reads each outstanding SAFE's own valuation cap, discount and MFN from the record — do not ask the user for a cap, and do not offer hypothetical caps; they are already stored. Nor do you need share counts first. Use this for a raise that has no round yet. PreviewCloseCapTableRound requires an existing round and cannot answer the same question. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.
cap_table_simulate_cap_table_dilution accepts 4 parameters: companyId, newMoneyRaise, preMoneyValuation, targetOptionPoolPct. 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_simulate_cap_table_dilution: 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_simulate_cap_table_dilution is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cap_table_simulate_cap_table_dilution 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_simulate_cap_table_dilution. 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_simulate_cap_table_dilution 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.
This server
Across the catalogue