signature_void_envelope
VoidSignatureEnvelope voids an envelope (owner-gated, ownership checked like SignAsCompany): writes a terminal DOCUMENT_VOIDED status + voided_at and appends a hash-chained document_voided event. Voiding a completed (executed) envelope requires a reason. Voided envelopes are excluded from the pip...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/signature-void-envelope.md
What signature_void_envelope does on Lovie Company Formation MCP
AI agents call signature_void_envelope 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 |
|---|---|---|---|
reason | string | — | |
ipAddress | string | — | |
userAgent | string | — | |
envelopeId | string | — | |
geoLocation | string | — |
Parameters from the server's own tool schema.
Why signature_void_envelope is rated Critical
An AI agent that decides to call signature_void_envelope 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 signature_void_envelope 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 signature_void_envelope, this is the rule to start with:
signature_void_envelope 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 signature_void_envelope call is checked against it from then on.
Questions about signature_void_envelope
VoidSignatureEnvelope voids an envelope (owner-gated, ownership checked like SignAsCompany): writes a terminal DOCUMENT_VOIDED status + voided_at and appends a hash-chained document_voided event. Voiding a completed (executed) envelope requires a reason. Voided envelopes are excluded from the pipeline Signed derivation, so the investor reverts to Committed and can be re-sent. Exposed as the counterpart to opening an envelope: a caller that can send one should be able to cancel one. The destructive case is guarded in the domain rather than by obscurity — ownership is checked, the row is never deleted, and voiding an executed envelope requires a reason. The destructive annotation is what makes a client confirm before calling it. One consequence of exposing it: ip_address, user_agent and geo_location on VoidSignatureEnvelopeRequest are caller-supplied and land verbatim in the hash-chained document_voided event. The chain stays tamper-evident, but on a rescission of an executed agreement those three fields are now written by whatever an MCP client sends rather than by a browser route reading the real request. Server-deriving them at the handler would fix it; not done here. 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.
signature_void_envelope accepts 5 parameters: reason, ipAddress, userAgent, envelopeId, geoLocation. 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 signature_void_envelope: 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.
signature_void_envelope 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 signature_void_envelope 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 signature_void_envelope. 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.
signature_void_envelope 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