brc_create_cash_payment
Creates a BRC cash payment. Use supplierId + ledger for supplier payments, bankAccountId + lodgement for bank lodgements, or analysisCategoryId + accountCode for analysed expenses. Analysis categories must be from the Cash Payments book (CP01-CP03) and accountCode must match the category. Require...
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-create-cash-payment.md
What brc_create_cash_payment does on Red by Big Red Cloud
AI agents use brc_create_cash_payment 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 |
|---|---|---|---|
note | string | Yes | |
total | number | Yes | |
acCode | string | — | Supplier account code for ledger payments. |
ledger | number | — | Ledger amount; must equal total for supplier payments. |
discount | number | — | |
procDate | string | — | Processing date in ISO format. Defaults to entryDate. |
entryDate | string | — | Entry date in ISO format. Defaults to today. |
lodgement | number | — | Lodgement amount; must equal total when lodging to bank. |
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 |
supplierId | integer | — | Supplier id for ledger payments. |
accountCode | string | — | Analysis account code matching analysisCategoryId, for example CP01. |
companyName | string | Yes | Company context name, for example YOUR-COMPANY-NAME. |
Parameters from the server's own tool schema.
Why brc_create_cash_payment is rated Medium
An AI agent can call brc_create_cash_payment 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.
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs brc_create_cash_payment 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_create_cash_payment, this is the rule to start with:
brc_create_cash_payment 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 Red by Big Red Cloud, apply this rule, and every brc_create_cash_payment call is checked against it from then on.
Questions about brc_create_cash_payment
Creates a BRC cash payment. Use supplierId + ledger for supplier payments, bankAccountId + lodgement for bank lodgements, or analysisCategoryId + accountCode for analysed expenses. Analysis categories must be from the Cash Payments book (CP01-CP03) and accountCode must match the category. 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.
brc_create_cash_payment accepts 12 parameters: note, total, acCode, ledger, discount, procDate, entryDate, lodgement, routeToken, supplierId, accountCode, companyName. Required: note, total, routeToken, companyName. The full parameter table on this page comes from the server's own tool schema.
Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_create_cash_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 Red by Big Red Cloud. Nothing to install.
brc_create_cash_payment 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 brc_create_cash_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 brc_create_cash_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.
brc_create_cash_payment 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.
More on Red by Big Red Cloud, and thousands of servers like it.
This server
Across the catalogue