accounting_suggest_transfer_pairs
Rank the journal entries that could be the other half of a transfer between the company's own accounts: opposite direction, same amount, different instrument, dated within a few days. Writes nothing — apply one with accounting_confirm_transfer_pair.
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/accounting-suggest-transfer-pairs.md
What accounting_suggest_transfer_pairs does on Lovie Company Formation MCP
AI agents use accounting_suggest_transfer_pairs to commit financial operations through Lovie Company Formation MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | object | Yes | UUID value wrapper. |
journalEntryId | object | Yes | UUID value wrapper. |
Parameters from the server's own tool schema.
Why accounting_suggest_transfer_pairs is rated Critical
accounting_suggest_transfer_pairs moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs accounting_suggest_transfer_pairs 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 accounting_suggest_transfer_pairs, this is the rule to start with:
Any call to accounting_suggest_transfer_pairs is blocked until a human approves 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 accounting_suggest_transfer_pairs call is checked against it from then on.
Questions about accounting_suggest_transfer_pairs
Rank the journal entries that could be the other half of a transfer between the company's own accounts: opposite direction, same amount, different instrument, dated within a few days. Writes nothing — apply one with accounting_confirm_transfer_pair. It is categorised as a Financial tool in the Lovie Company Formation MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
accounting_suggest_transfer_pairs accepts 2 parameters: companyId, journalEntryId. Required: companyId, journalEntryId. 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 accounting_suggest_transfer_pairs: 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.
accounting_suggest_transfer_pairs is a Financial 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 accounting_suggest_transfer_pairs 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 accounting_suggest_transfer_pairs. 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.
accounting_suggest_transfer_pairs 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