accounting_batch_set_excluded
Exclude up to 500 transactions from the books (set excluded=true) or put them back (excluded=false). Excluding voids the transaction's journal entry and stops the posting engine from re-deriving it, so the amount leaves every report. Use for duplicates, personal spending on a business card, and t...
This record as markdown: /tools/lovieco-lovie-company-formation-mcp-npx/accounting-batch-set-excluded.md
What accounting_batch_set_excluded does on Lovie Company Formation MCP
AI agents use accounting_batch_set_excluded 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 |
|---|---|---|---|
reason | string | — | |
excluded | boolean | — | |
companyId | object | Yes | UUID value wrapper. |
transactionIds | array | — |
Parameters from the server's own tool schema.
Why accounting_batch_set_excluded is rated Medium
An AI agent can call accounting_batch_set_excluded 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 accounting_batch_set_excluded 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_batch_set_excluded, this is the rule to start with:
accounting_batch_set_excluded 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 accounting_batch_set_excluded call is checked against it from then on.
Questions about accounting_batch_set_excluded
Exclude up to 500 transactions from the books (set excluded=true) or put them back (excluded=false). Excluding voids the transaction's journal entry and stops the posting engine from re-deriving it, so the amount leaves every report. Use for duplicates, personal spending on a business card, and transfers already recorded elsewhere. 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.
accounting_batch_set_excluded accepts 4 parameters: reason, excluded, companyId, transactionIds. Required: companyId. 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_batch_set_excluded: 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_batch_set_excluded 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 accounting_batch_set_excluded 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_batch_set_excluded. 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_batch_set_excluded 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