documents_delete_saved_signature
DeleteSavedSignature removes one of the caller's saved signatures. Exposed because ListSavedSignatures already is: the agent could name a founder's signatures without being able to clear a stale one. The row it removes is not recoverable, so it is annotated destructive — that hint is what makes c...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/documents-delete-saved-signature.md
What documents_delete_saved_signature does on Lovie Company Formation MCP
AI agents call documents_delete_saved_signature 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 |
|---|---|---|---|
companyId | object | Yes | UUID value wrapper. |
savedSignatureId | object | Yes | UUID value wrapper. |
Parameters from the server's own tool schema.
Why documents_delete_saved_signature is rated Critical
An AI agent that decides to call documents_delete_saved_signature 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 documents_delete_saved_signature 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 documents_delete_saved_signature, this is the rule to start with:
documents_delete_saved_signature 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 documents_delete_saved_signature call is checked against it from then on.
Questions about documents_delete_saved_signature
DeleteSavedSignature removes one of the caller's saved signatures. Exposed because ListSavedSignatures already is: the agent could name a founder's signatures without being able to clear a stale one. The row it removes is not recoverable, so it is annotated destructive — that hint is what makes clients confirm before calling it. 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.
documents_delete_saved_signature accepts 2 parameters: companyId, savedSignatureId. Required: companyId, savedSignatureId. 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 documents_delete_saved_signature: 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.
documents_delete_saved_signature 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 documents_delete_saved_signature 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 documents_delete_saved_signature. 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.
documents_delete_saved_signature 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