brc_batch_sales_invoices

SERVERRed by Big Red Cloud SOURCEhttps://red.bigredcloud.com/mcp

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-batch-sales-invoices.md

WHAT IT DOES

What brc_batch_sales_invoices does on Red by Big Red Cloud

AI agents use brc_batch_sales_invoices to create or update resources in Red by Big Red Cloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Red by Big Red Cloud environment.

Parameter	Type	Required	Description
`items`	array	Yes	Batch items to process. Maximum 20 items per request.
`priceBasis`	string	—	Applies to every sales invoice/credit note item in this batch. Required when Gross Price Entry is enabled. Use `gross` when unit prices are VAT-inclusive/gross.
`routeToken`	string	Yes	Opaque routeToken from brc_route_request for this action workflow. Required for transactional tools. Routing permission only — does not replace preview-before-p
`companyName`	string	Yes	Company context name, for example YOUR-COMPANY-NAME.
`confirmWrite`	boolean	—	Must be true only after a plain-English preview before posting has been shown in the current conversation and the user explicitly confirmed posting (for example
`connectionRef`	string	—	Opaque Red connection reference returned by brc_confirm_company_connection. Pass this exact value on every later tool call when the MCP client rotates session i
`confirmCrAnalysisCategory`	boolean	—	Applies to every sales document item in this batch. Set true only after the user confirms a CR (customer) sales analysis account code is intentional for these p
`confirmCounterpartyExplicit`	boolean	—	Must be true only after the user explicitly named or confirmed the customer, supplier, or other counterparty in the current conversation. Never set true because

Parameters from the server's own tool schema.

RISK

Why brc_batch_sales_invoices is rated Medium

An AI agent can call brc_batch_sales_invoices faster than any human can review: one bad instruction and it creates or modifies resources in Red by Big Red Cloud by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brc_batch_sales_invoices safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Red by Big Red Cloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brc_batch_sales_invoices, this is the rule to start with:

brc_batch_sales_invoices Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "brc_batch_sales_invoices": {
      "limits": [
        {
          "counter": "brc_batch_sales_invoices_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Red by Big Red Cloud, apply this rule, and every brc_batch_sales_invoices call is checked against it from then on.

FAQ

Questions about brc_batch_sales_invoices

What does the brc_batch_sales_invoices tool do? +

Processes a batch of sales invoices. Batch sales invoices apply the same safety checks as single sales invoices: productId 0/1 placeholder blocking before preview-before-posting and posting; Sales VAT category validation before preview-before-posting and posting; Gross Price Entry priceBasis handling; CR analysis category confirmation; and counterparty confirmation covering all listed customers. If the batch includes multiple customers, confirming means confirming all listed customers, not just one. Set confirmCrAnalysisCategory=true at batch level only after the user confirms CR sales analysis account codes are intentional. Per item, the BRC "Note" field (JSON note) defaults to the customer name when omitted (never the product name), and the BRC "Delivery To" address (JSON deliveryTo) is only included when explicitly provided. Do not invent productId values and do not use productId 0 or 1 as placeholders. productId 0 and 1 are treated as placeholders and are blocked at runtime before preview-before-posting and before posting. If a product line is needed, first call brc_list_products and use a real product from the connected company. If no suitable product exists, ask the user whether to create/select a product, or use a service/non-product line only if the endpoint supports it. Sales invoices must use Sales VAT rates. Purchase/non-Sales VAT rates are blocked before preview-before-posting and before posting, even if the VAT percentage matches. Maximum 20 items per batch request. Requires routeToken from brc_route_request for the matching action workflow. Call brc_route_request first with the user's complete original action request. Retain the returned routeToken through lookup, preview, and confirmation, and pass the same token on the final permitted transactional tool call. Never invent a placeholder token. A routeToken is not permission to post — preview-before-posting and confirmWrite/confirmDelete still apply. Also requires confirmCounterpartyExplicit: true once the user has explicitly named or confirmed the customer/supplier in the current conversation. Do not reuse a counterparty from an earlier preview without that confirmation. It is categorised as a Write tool in the Red by Big Red Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does brc_batch_sales_invoices accept? +

brc_batch_sales_invoices accepts 8 parameters: items, priceBasis, routeToken, companyName, confirmWrite, connectionRef, confirmCrAnalysisCategory, confirmCounterpartyExplicit. Required: items, routeToken, companyName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_batch_sales_invoices? +

Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_batch_sales_invoices: 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 Red by Big Red Cloud. Nothing to install.

What risk level is brc_batch_sales_invoices? +

brc_batch_sales_invoices is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit brc_batch_sales_invoices? +

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

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

brc_batch_sales_invoices is provided by the Red by Big Red Cloud MCP server (https://red.bigredcloud.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Red by Big Red Cloud, and thousands of servers like it.

This server

All 159 Red by Big Red Cloud tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →