cap_table_set_cap_table_pipeline_status

Moves ONE investor's holding along the fundraising pipeline. Use this to change a stage — never UpdateCapTableSecurity, which is a full replace and will blank any field you do not resend. Forward goes one stage at a time (committed -> sent -> signed; awaiting_middleman sits between sent and signed and applies only to deals routed through a middleman), with one exception: 'signed' can be set from any earlier stage, because a countersigned agreement can arrive without ever having been sent. Never step through 'sent' to reach 'signed' when nothing was sent — that records a send that did not happen. Moving BACK to an earlier stage is allowed and is how a stage entered by mistake gets corrected — no need to delete the investor. Two things cannot be undone: 'wired' is set only by recording the wire (RecordCapTableWire, which requires a matched bank transaction or a verified payment proof) and never by this tool, and once wired the only move is a refund (RecordCapTableRefund). Setting the stage a holding already has is accepted and changes nothing. The fundraising pipeline is investors only: founders and employees receive equity, they never commit or wire capital, so a stage move on their holding is refused — leave them out when you list or summarize the pipeline. 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_set_cap_table_pipeline_status accepts 3 parameters: companyId, securityId, pipelineStatus. Required: companyId, securityId. 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_set_cap_table_pipeline_status: 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_set_cap_table_pipeline_status 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_set_cap_table_pipeline_status 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_set_cap_table_pipeline_status. 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_set_cap_table_pipeline_status 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.