cap_table_record_cap_table_wire
Records an investor wire into the money-movement ledger and flips the security's pipeline_status to 'wired'. A wire is accepted ONLY when it is backed by one of: (a) a matched banking transaction_id (see GetListCapTableWireMatchSuggestions), or (b) a proof_document_uri whose ExtractWirePaymentPro...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/cap-table-record-cap-table-wire.md
What cap_table_record_cap_table_wire does on Lovie Company Formation MCP
AI agents call cap_table_record_cap_table_wire 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 |
|---|---|---|---|
amount | string | — | |
companyId | object | Yes | UUID value wrapper. |
reference | string | — | |
occurredAt | string | — | |
securityId | object | Yes | UUID value wrapper. |
ocrConfidence | string | — | |
reviewedProof | object | — | |
transactionId | object | — | UUID value wrapper. |
proofDocumentUri | string | — |
Parameters from the server's own tool schema.
Why cap_table_record_cap_table_wire is rated Low
Even though cap_table_record_cap_table_wire 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.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs cap_table_record_cap_table_wire 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_record_cap_table_wire, this is the rule to start with:
cap_table_record_cap_table_wire 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_record_cap_table_wire call is checked against it from then on.
Questions about cap_table_record_cap_table_wire
Records an investor wire into the money-movement ledger and flips the security's pipeline_status to 'wired'. A wire is accepted ONLY when it is backed by one of: (a) a matched banking transaction_id (see GetListCapTableWireMatchSuggestions), or (b) a proof_document_uri whose ExtractWirePaymentProof verdict is 'verified'. With neither, the call is rejected — never mark a wire wired without a matched transaction or a verified payment proof. 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_record_cap_table_wire accepts 9 parameters: amount, companyId, reference, occurredAt, securityId, ocrConfidence, reviewedProof, transactionId, proofDocumentUri. 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_record_cap_table_wire: 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_wire 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_record_cap_table_wire 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_wire. 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_wire 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