cap_table_delete_cap_table_round
DeleteCapTableRound permanently removes an unpriced SAFE round (open or light-closed) plus its round-scoped securities/agreements/snapshots. Priced / engine-closed rounds are rejected (FailedPrecondition).
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/cap-table-delete-cap-table-round.md
What cap_table_delete_cap_table_round does on Lovie Company Formation MCP
AI agents call cap_table_delete_cap_table_round to permanently remove resources in Lovie Company Formation MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
roundId | object | Yes | UUID value wrapper. |
companyId | object | Yes | UUID value wrapper. |
Parameters from the server's own tool schema.
Why cap_table_delete_cap_table_round is rated Critical
An AI agent that decides to call cap_table_delete_cap_table_round doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Lovie Company Formation MCP is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cap_table_delete_cap_table_round 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_delete_cap_table_round, this is the rule to start with:
cap_table_delete_cap_table_round is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lovie Company Formation MCP, apply this rule, and every cap_table_delete_cap_table_round call is checked against it from then on.
Questions about cap_table_delete_cap_table_round
DeleteCapTableRound permanently removes an unpriced SAFE round (open or light-closed) plus its round-scoped securities/agreements/snapshots. Priced / engine-closed rounds are rejected (FailedPrecondition). It is categorised as a Destructive tool in the Lovie Company Formation MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cap_table_delete_cap_table_round accepts 2 parameters: roundId, companyId. Required: roundId, 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_delete_cap_table_round: 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_delete_cap_table_round is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cap_table_delete_cap_table_round 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_delete_cap_table_round. 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_delete_cap_table_round 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