draft_payment
Draft a payment for human review: returns a canonical, ready-to-sign Mandate (body JSON + JCS hash) and a plain-language summary. Does NOT move money or run the pipeline — a human commits it by signing and submitting.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/draft-payment.md
What draft_payment does on Lovie Company Formation MCP
AI agents invoke draft_payment to trigger actions in Lovie Company Formation MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
memo | string | — | |
rail | string | — | |
signerId | string | — | |
companyId | string | — | |
customerId | string | — | |
amountCents | integer | — | |
keyFingerprint | string | — | |
accountNumberId | string | — | |
counterpartyRef | string | — | |
expiresInSeconds | integer | — |
Parameters from the server's own tool schema.
Why draft_payment is rated High
draft_payment triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs draft_payment 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 draft_payment, this is the rule to start with:
draft_payment stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 draft_payment call is checked against it from then on.
Questions about draft_payment
Draft a payment for human review: returns a canonical, ready-to-sign Mandate (body JSON + JCS hash) and a plain-language summary. Does NOT move money or run the pipeline — a human commits it by signing and submitting. It is categorised as a Execute tool in the Lovie Company Formation MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
draft_payment accepts 10 parameters: memo, rail, signerId, companyId, customerId, amountCents, keyFingerprint, accountNumberId, counterpartyRef, expiresInSeconds. 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 draft_payment: 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.
draft_payment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the draft_payment 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 draft_payment. 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.
draft_payment 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