# cap_table_import_safe

Imports a SAFE from an uploaded SAFE PDF and stores the document in S3. USE THIS (not RecordCapTableInvestment) whenever the user provides or uploads a SAFE PDF file. Flow: (1) call GetOcrUploadUrl with kind=SAFE and mime_type=application/pdf to get a presigned PUT URL + source_s3_uri, (2) upload the PDF bytes to that PUT URL, (3) call ImportSAFE with that source_s3_uri. This runs OCR to extract the terms; pass valuation_cap / investment_amount / discount_rate only to CORRECT a value the user says the OCR misread, and leave them empty to keep what the document says. Call ExtractSafeTerms first and get the user's confirmation before importing. effective_date is required — never import a SAFE without a date. If the company named on the document differs from this company, say both names and get the user's confirmation before importing. It copies the PDF to the canonical cap-table SAFE location, links it to a SAFE agreement, resolves the investor by name (matching an existing stakeholder or creating a new one), and papers that investor's existing SAFE holding (the one carrying the document's amount, else their only unfunded one) rather than creating a second; only with none to paper does it create the security. Pass security_id to name the exact holding to paper (the web investor card does). An unsent generated SAFE draft that the import replaces is voided. With security_id naming the holding, the import is refused with FAILED_PRECONDITION when that investor already has a SAFE signed or out for signature (the user must void that envelope first) or when a wired holding's amount differs from the document's; a typed investment_amount does not unlock a wired holding. A document_id whose hub row is itself out for signature is refused with FAILED_PRECONDITION even without security_id, as is one already filed for another record (including a second submit of the same document). WITHOUT security_id, an investor whose SAFE is already signed or out for signature gets an additional SAFE holding beside it rather than a refusal — tell the user a second SAFE was recorded for that investor. Either way, the import is refused when the investor's SAFE signing state cannot be confirmed: when the document hub is unreachable tell the user to try again shortly, and when that SAFE is not filed in documents tell them support has to file it first. Pass post_money=true only when the user says the SAFE is post-money and the extraction did not; false leaves the document's own answer. A preview whose investor_name is empty found no investor named on the document: ask the user who the investor is and pass new_stakeholder_name on the import. The security is marked signed only if the document is actually signed; an unsigned SAFE PDF is still stored and left committed. Whenever the user has the PDF — including when they attached it to this conversation — upload it and pass source_s3_uri so the document itself is stored; a SAFE created from typed terms alone has nothing on record proving its date or signature, and the cap table flags it as missing its document. Use RecordCapTableInvestment only for a SAFE the user genuinely has no document for. 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.

Agent View of the PolicyLayer registry record for `cap_table_import_safe`. HTML page: https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-import-safe

## Facts

- Tool: `cap_table_import_safe`
- Server: Lovie Company Formation MCP (`lovie`) — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx.md
- Install: `npx -y lovie`
- Homepage: https://github.com/lovieco/lovie-company-formation-mcp-npx
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 12 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `preview` | boolean | no |  |
| `roundId` | object | no | UUID value wrapper. |
| `companyId` | object | yes | UUID value wrapper. |
| `postMoney` | boolean | no |  |
| `documentId` | object | no | UUID value wrapper. |
| `securityId` | object | no | UUID value wrapper. |
| `sourceS3Uri` | string | no |  |
| `discountRate` | string | no |  |
| `valuationCap` | string | no |  |
| `effectiveDate` | string | no |  |
| `stakeholderId` | object | no | UUID value wrapper. |
| `consentToAiRead` | boolean | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cap_table_import_safe",
    "arguments": {
      "companyId": {}
    }
  }
}
```

## Why cap_table_import_safe is rated Medium

An AI agent can call cap_table_import_safe faster than any human can review: one bad instruction and it creates or modifies resources in Lovie Company Formation MCP by the hundred, each call as confident as the last.

Risk signals: High parameter count (20 properties)

## Use case

AI agents use cap_table_import_safe to create or update resources in Lovie Company Formation MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lovie Company Formation MCP environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Lovie Company Formation MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cap_table_import_safe": {
      "limits": [
        {
          "counter": "cap_table_import_safe_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Lovie Company Formation MCP (339)

- `accounting_cancel_schedule` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/accounting-cancel-schedule.md
- `accounting_confirm_statement_match` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/accounting-confirm-statement-match.md
- `accounting_delete_journal_entry` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/accounting-delete-journal-entry.md
- `cap_table_clear_cap_table_stakeholders` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-clear-cap-table-stakeholders.md
- `cap_table_close_cap_table_round` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-close-cap-table-round.md
- `cap_table_delete_cap_table_agreement` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-delete-cap-table-agreement.md
- `cap_table_delete_cap_table_round` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-delete-cap-table-round.md
- `cap_table_delete_cap_table_security` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-delete-cap-table-security.md
- `cap_table_delete_cap_table_stakeholder` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-delete-cap-table-stakeholder.md
- `cap_table_set_cap_table_pipeline_status` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-set-cap-table-pipeline-status.md
- `documents_delete_saved_signature` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/documents-delete-saved-signature.md
- `formation_delete_pending_domain` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/formation-delete-pending-domain.md
- `formation_remove_shareholder` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/formation-remove-shareholder.md
- `signature_void_envelope` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/signature-void-envelope.md
- `trademark_delete_application` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/trademark-delete-application.md
- `vendor_bill_cancel_vendor_bill` — Destructive — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/vendor-bill-cancel-vendor-bill.md
- `accounting_propose_schedules` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/accounting-propose-schedules.md
- `ads_insight_summarize_campaign_window` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/ads-insight-summarize-campaign-window.md
- `banking_refresh_owner_verification` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/banking-refresh-owner-verification.md
- `banking_start_banking_application` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/banking-start-banking-application.md
- `cap_table_record_cap_table_investment` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-record-cap-table-investment.md
- `cap_table_simulate_cap_table_exit` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/cap-table-simulate-cap-table-exit.md
- `draft_payment` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/draft-payment.md
- `equity_onboarding_start` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/equity-onboarding-start.md
- `formation_run_election83b_reminders` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/formation-run-election83b-reminders.md
- `formation_start_formation` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/formation-start-formation.md
- `kyc_start_kyc_inquiry` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/kyc-start-kyc-inquiry.md
- `signature_reconcile_document_state` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/signature-reconcile-document-state.md
- `signature_run_reminders` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/signature-run-reminders.md
- `trademark_run_clearance` — Execute — https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx/trademark-run-clearance.md
- …and 309 more: https://policylayer.com/tools/lovieco-lovie-company-formation-mcp-npx.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=lovieco-lovie-company-formation-mcp-npx · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/lovieco-lovie-company-formation-mcp-npx