signature_signing_status

GetEnvelopeSigners lists an envelope's signers and their signing progress.

SERVERLovie Company Formation MCP SOURCElovie

Low RISK CLASS

Category Read

Parameters 10 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/signature-signing-status.md

WHAT IT DOES

What signature_signing_status does on Lovie Company Formation MCP

AI agents call signature_signing_status 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
`envelopeId`	string	—

Parameters from the server's own tool schema.

RISK

Why signature_signing_status is rated Low

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs signature_signing_status 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_signing_status, this is the rule to start with:

signature_signing_status Allowed

signature_signing_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "signature_signing_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lovie Company Formation MCP, apply this rule, and every signature_signing_status call is checked against it from then on.

FAQ

Questions about signature_signing_status

What does the signature_signing_status tool do? +

GetEnvelopeSigners lists an envelope's signers and their signing progress. 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 signature_signing_status accept? +

signature_signing_status accepts 1 parameter: envelopeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on signature_signing_status? +

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

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

Can I rate-limit signature_signing_status? +

Yes. Add a rate_limit block to the signature_signing_status 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 signature_signing_status completely? +

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

signature_signing_status 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.

KEEP EXPLORING

More on Lovie Company Formation, and thousands of servers like it.

This server

All 340 Lovie Company Formation tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →