signature_resend_signer_invite
ResendSignerInvite rotates a signer's token and re-emails the signing link to the persisted signer email. Founder-gated. Exposed. The earlier reason for holding it closed — "mints a token" — did not describe the risk: ResendSignerInviteResponse is empty, so the token reaches the signer by email a...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/signature-resend-signer-invite.md
What signature_resend_signer_invite does on Lovie Company Formation MCP
AI agents use signature_resend_signer_invite 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
signerId | string | — |
Parameters from the server's own tool schema.
Why signature_resend_signer_invite is rated Medium
An AI agent can call signature_resend_signer_invite 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs signature_resend_signer_invite 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_resend_signer_invite, this is the rule to start with:
signature_resend_signer_invite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 signature_resend_signer_invite call is checked against it from then on.
Questions about signature_resend_signer_invite
ResendSignerInvite rotates a signer's token and re-emails the signing link to the persisted signer email. Founder-gated. Exposed. The earlier reason for holding it closed — "mints a token" — did not describe the risk: ResendSignerInviteResponse is empty, so the token reaches the signer by email and never the caller. The real effect is rotation: every link emailed to that signer earlier stops working, which is why this carries WRITE risk rather than being treated as a read. It is categorised as a Write tool in the Lovie Company Formation MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
signature_resend_signer_invite accepts 1 parameter: signerId. 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_resend_signer_invite: 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_resend_signer_invite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the signature_resend_signer_invite 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_resend_signer_invite. 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_resend_signer_invite 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