New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cap_table_extract_wire_payment_proof

Runs vision OCR on an already-uploaded wire payment proof (wire confirmation, bank statement, or transfer receipt — NOT an invoice) for a security and returns the extracted fields plus a verification verdict (verified | needs_review | mismatch). Nothing is persisted. Flow: call GetOcrUploadURL wi...

Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/cap-table-extract-wire-payment-proof.md

What cap_table_extract_wire_payment_proof does on Lovie Company Formation MCP

AI agents call cap_table_extract_wire_payment_proof 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.

ParameterTypeRequiredDescription
agentCode string —
companyId object Yes UUID value wrapper.
securityId object Yes UUID value wrapper.
sourceS3Uri string —

Parameters from the server's own tool schema.

Why cap_table_extract_wire_payment_proof is rated Low

Even though cap_table_extract_wire_payment_proof 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.

Questions about cap_table_extract_wire_payment_proof

What does the cap_table_extract_wire_payment_proof tool do? +

Runs vision OCR on an already-uploaded wire payment proof (wire confirmation, bank statement, or transfer receipt — NOT an invoice) for a security and returns the extracted fields plus a verification verdict (verified | needs_review | mismatch). Nothing is persisted. Flow: call GetOcrUploadURL with kind=WIRE_PROOF, PUT the file bytes to the returned upload_url, then call this with the returned source_s3_uri. Only a 'verified' verdict can back a wire in RecordCapTableWire. It is categorised as a Read tool in the Lovie Company Formation MCP MCP Server, which means it retrieves data without modifying state.

What parameters does cap_table_extract_wire_payment_proof accept? +

cap_table_extract_wire_payment_proof accepts 4 parameters: agentCode, companyId, securityId, sourceS3Uri. Required: companyId, securityId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cap_table_extract_wire_payment_proof? +

Register the Lovie Company Formation MCP server in PolicyLayer and add a rule for cap_table_extract_wire_payment_proof: 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.

What risk level is cap_table_extract_wire_payment_proof? +

cap_table_extract_wire_payment_proof is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cap_table_extract_wire_payment_proof? +

Yes. Add a rate_limit block to the cap_table_extract_wire_payment_proof 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.

How do I block cap_table_extract_wire_payment_proof completely? +

Set action: deny in the PolicyLayer policy for cap_table_extract_wire_payment_proof. 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.

What MCP server provides cap_table_extract_wire_payment_proof? +

cap_table_extract_wire_payment_proof 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Lovie Company Formation's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.